Update articles/getting_started/content_pipeline/content_builder_project.md

SimonDarksideJ · Copilot · web-flow · commit 48ec3df08362 · 2025-11-09T10:34:53.000Z
Co-authored-by: Copilot &lt;175728472+Copilot@users.noreply.github.com&gt;
diff --git a/articles/getting_started/content_pipeline/content_builder_project.md b/articles/getting_started/content_pipeline/content_builder_project.md
@@ -33,7 +33,7 @@ Instead of an installed dotnet tool (which historically generated issues), the n
 > [!TIP]
 > When designing the builder for your content, try to focus on building patterns for your content to reduce the need to rebuild the `Builder` itself.
 >
-> In an ideal scenario, you build the `Builder` once, then just keep adding assets and running the builder to produce the runtime content, identifying "early on" any issus with your assets and simplifying production.
+> In an ideal scenario, you build the `Builder` once, then just keep adding assets and running the builder to produce the runtime content, identifying "early on" any issues with your assets and simplifying production.
 
 In addition, due to content now being built through your own console application, it is easily distributable and can even be used in automation pipelines in source control.
 

Original file line number	Diff line number	Diff line change
`@@ -33,7 +33,7 @@ Instead of an installed dotnet tool (which historically generated issues), the n`
`33`	`33`	`> [!TIP]`
`34`	`34`	> When designing the builder for your content, try to focus on building patterns for your content to reduce the need to rebuild the `Builder` itself.
`35`	`35`	`>`
`36`		-> In an ideal scenario, you build the `Builder` once, then just keep adding assets and running the builder to produce the runtime content, identifying "early on" any issus with your assets and simplifying production.
	`36`	+> In an ideal scenario, you build the `Builder` once, then just keep adding assets and running the builder to produce the runtime content, identifying "early on" any issues with your assets and simplifying production.
`37`	`37`
`38`	`38`	`In addition, due to content now being built through your own console application, it is easily distributable and can even be used in automation pipelines in source control.`
`39`	`39`