Skip to content

Commit dec8fe4

Browse files
Update articles/getting_started/content_pipeline/content_builder_project.md
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent 48ec3df commit dec8fe4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/getting_started/content_pipeline/content_builder_project.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ MyContentBuilder/
100100
This is the default (recommended) layout for a Content Builder project, but you can customize its use how you wish:
101101

102102
- There is single "entry point" (command line launch point) contained in the `builder.cs` which contains all the instructions to build content.
103-
- A default `Assets` folder to host your content, but you content can be in any location you need it to be, simply update the parameters used to run the console application to point to the source directory and folder for your content.
103+
- A default `Assets` folder to host your content, but your content can be in any location you need it to be, simply update the parameters used to run the console application to point to the source directory and folder for your content.
104104

105105
> [!TIP]
106106
> While it is possible to include the builder as part of your game code, rather than a separate project, at this time we do not recommend this. Based on experience, it is always better to build your content separate from your runtime game to avoid collisions or issues arising in game production/deployment.

0 commit comments

Comments
 (0)