gohugoio · jmooring · Feb 24, 2026 · Feb 24, 2026
diff --git a/content/en/configuration/output-formats.md b/content/en/configuration/output-formats.md
@@ -138,7 +138,7 @@ Step 4
 
 ## List output formats
 
-To access output formats, each `Page` object provides two methods: [`OutputFormats`][] (for all formats, including the current one) and [`AlternativeOutputFormats`][]. Use `AlternativeOutputFormats` to create a link `rel` list within your site's `head` element, as shown below:
+To access output formats, each `Page` object provides two methods: [`OutputFormats`][] (for all formats, including the current one) and [`AlternativeOutputFormats`][]. Use `AlternativeOutputFormats` to create a link `rel` list within a `head` element, as shown below:
 
 ```go-html-template
 {{ range .AlternativeOutputFormats }}

diff --git a/content/en/configuration/outputs.md b/content/en/configuration/outputs.md
@@ -41,7 +41,7 @@ title = 'Example'
 outputs = ['json']
 {{< /code-toggle >}}
 
-In its default configuration, Hugo will render both the `html` and `json` output formats for this page. The `outputs` field appends to, rather than replaces, the site's configured outputs.
+In its default configuration, Hugo will render both the `html` and `json` output formats for this page. The `outputs` field appends to, rather than replaces, the project's configured outputs.
 
 [`Permalink`]: /methods/page/permalink/
 [`RelPermalink`]: /methods/page/relpermalink/

diff --git a/content/en/content-management/comments.md b/content/en/content-management/comments.md
@@ -16,7 +16,7 @@ Hugo comes with all the code you need to load Disqus into your templates. Before
 
 ### Configure Disqus
 
-Disqus comments require you set a single value in your [site's configuration file][configuration] like so:
+Disqus comments require you set a single value in your [project configuration][configuration]:
 
 {{< code-toggle file=hugo >}}
 [services.disqus]

diff --git a/content/en/content-management/organization/index.md b/content/en/content-management/organization/index.md
@@ -61,7 +61,7 @@
 
 ## Path breakdown in Hugo
 
-The following demonstrates the relationships between your content organization and the output URL structure for your Hugo website when it renders. These examples assume you are [using pretty URLs][pretty], which is the default behavior for Hugo. The examples also assume a key-value of `baseURL = "https://example.org/"` in your [site's configuration file][config].
+The following demonstrates the relationships between your content organization and the output URL structure for your Hugo website when it renders. These examples assume you are [using pretty URLs][pretty], which is the default behavior for Hugo. The examples also assume a key-value of `baseURL = "https://example.org/"` in your [prject configuration][config].
 
 ### Index pages: `_index.md`
 

diff --git a/content/en/content-management/shortcodes.md b/content/en/content-management/shortcodes.md
@@ -42,7 +42,7 @@ An inline shortcode is a _shortcode_ template defined within content.
 
 Hugo's security model is based on the premise that template and configuration authors are trusted, but content authors are not. This model enables generation of HTML output safe against code injection.
 
-To conform with this security model, creating _shortcode_ templates within content is disabled by default. If you trust your content authors, you can enable this functionality in your site's configuration:
+To conform with this security model, creating _shortcode_ templates within content is disabled by default. If you trust your content authors, you can enable this functionality in your project configuration:
 
 {{< code-toggle file=hugo >}}
 [security]

diff --git a/content/en/functions/css/Sass.md b/content/en/functions/css/Sass.md
@@ -130,7 +130,7 @@ To use Dart Sass with Hugo on a [CI/CD](g) platform, you typically must modify y
 There's one key exception where you can skip this step: you have committed your `resources` directory to your repository. This is only possible if:
 
 - You have not changed Hugo's default asset cache location.
-- You have not set [`useResourceCacheWhen`][] to never in your sites configuration.
+- You have not set [`useResourceCacheWhen`][] to never in your project configuration.
 
 By committing the `resources` directory, you're providing the pre-built CSS files directly to your CI/CD platform, so it doesn't need to run the Sass compilation itself.
 

diff --git a/content/en/functions/transform/Emojify.md b/content/en/functions/transform/Emojify.md
@@ -15,7 +15,7 @@ aliases: [/functions/emojify]
 
 See the list of [emoji shortcodes] for available emoticons.
 
-The `emojify` function can be called in your templates but not directly in your content files by default. For emojis in content files, set [`enableEmoji`] to `true` in your site's configuration. Then you can write emoji shorthand directly into your content files;
+The `emojify` function can be called in your templates but not directly in your content files by default. For emojis in content files, set [`enableEmoji`] to `true` in your project configuration. Then you can write emoji shorthand directly into your content files;
 
 ```text
 I :heart: Hugo!

diff --git a/content/en/templates/introduction.md b/content/en/templates/introduction.md
@@ -312,7 +312,7 @@ Object|Method|Description
 `Page`|[`Title`](methods/page/title/)|Returns the title of the given page.
 `Site`|[`Data`](methods/site/data/)|Returns a data structure composed from the files in the `data` directory.
 `Site`|[`Params`](methods/site/params/)|Returns a map of custom parameters as defined in your project configuration.
-`Site`|[`Title`](methods/site/title/)|Returns the title as defined in the site configuration.
+`Site`|[`Title`](methods/site/title/)|Returns the title as defined in the your project configuration.
 
 Chain the method to its object with a dot (`.`) as shown below, remembering that the leading dot represents the [current context].