Skip to content

Commit 483aa57

Browse files
committed
Update alt text: Reference #31
1 parent 97adb10 commit 483aa57

File tree

1 file changed

+2
-2
lines changed
  • articles/tutorials/building_2d_games/05_content_pipeline

1 file changed

+2
-2
lines changed

articles/tutorials/building_2d_games/05_content_pipeline/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -131,9 +131,9 @@ Now that we have added our first asset, we can take a moment to understand what
131131
132132
The following diagram demonstrates this workflow:
133133
134-
| ![Figure 5-7: MonoGame Content Pipeline Workflow](./images/content-pipeline-workflow-full.png) |
134+
| ![Figure 5-7: MonoGame Content Pipeline Workflow diagram showing the process flow from source files (Images, Audio, Fonts, Effects, Models) through the MGCB Editor to generate the Content.mgcb file, which is then processed by MonoGame.Content.Builder.Tasks to create compiled .xnb assets (Xnb formats for each type), which are finally loaded by the ContentManager at runtime](./images/content-pipeline-workflow-full.png) |
135135
| :--------------------------------------------------------------------------------------------: |
136-
| **Figure 5-7: MonoGame Content Pipeline Workflow** |
136+
| **Figure 5-7: MonoGame Content Pipeline Workflow diagram showing the process flow from source files (Images, Audio, Fonts, Effects, Models) through the MGCB Editor to generate the Content.mgcb file, which is then processed by MonoGame.Content.Builder.Tasks to create compiled .xnb assets (Xnb formats for each type), which are finally loaded by the ContentManager at runtime** |
137137
138138
The Content Pipeline offers significant advantages:
139139

0 commit comments

Comments
 (0)