Fixed some grammar issues and typos (#1865)

* Fixed some grammar issues and typos

* Update content/en/content-management/sections.md

Co-authored-by: Joe Mooring <joe@mooring.com>

* Update content/en/content-management/shortcodes.md

Co-authored-by: Joe Mooring <joe@mooring.com>

* Update content/en/getting-started/configuration.md

Co-authored-by: Joe Mooring <joe@mooring.com>

* Update content/en/hosting-and-deployment/hosting-on-netlify.md

Co-authored-by: Joe Mooring <joe@mooring.com>

* Update content/en/templates/menu-templates.md

Co-authored-by: Joe Mooring <joe@mooring.com>

* Update content/en/templates/menu-templates.md

Co-authored-by: Joe Mooring <joe@mooring.com>

* Update content/en/templates/shortcode-templates.md

Co-authored-by: Joe Mooring <joe@mooring.com>

Co-authored-by: Joe Mooring <joe@mooring.com>

25 files changed, 33 insertions, 33 deletions

diff --git a/content/en/content-management/sections.md b/content/en/content-management/sections.md
index 17fcb0817..d70bbea19 100644
--- a/content/en/content-management/sections.md
+++ b/content/en/content-management/sections.md
@@ -87,7 +87,7 @@ Also see [Page Variables](/variables/page/).
 
 ## Content Section Lists
 
-Hugo will automatically create pages for each *root section* that list all of the content in that section. See the documentation on [section templates][] for details on customizing the way these pages are rendered.
+Hugo will automatically create a page for each *root section* that lists all the content in that section. See the documentation on [section templates][] for details on customizing the way these pages are rendered.
 
 ## Content *Section* vs Content *Type*
 
diff --git a/content/en/content-management/shortcodes.md b/content/en/content-management/shortcodes.md
index 6b8a1e9ce..870af678b 100644
--- a/content/en/content-management/shortcodes.md
+++ b/content/en/content-management/shortcodes.md
@@ -176,7 +176,7 @@ If the gist contains several files and you want to quote just one of them, you c
 
 #### Example `gist` Display
 
-To demonstrate the remarkably efficiency of Hugo's shortcode feature, we have embedded the `spf13` `gist` example in this page. The following simulates the experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.
+To demonstrate the remarkable efficiency of Hugo's shortcode feature, we have embedded the `spf13` `gist` example in this page. The following simulates the experience for visitors to your website. Naturally, the final display will depend on your stylesheets and surrounding markup.
 
 {{< gist spf13 7896402 >}}
 
@@ -259,7 +259,7 @@ The `instagram`-shortcode refers an endpoint of Instagram's API, that's deprecat
 
 ### `param`
 
-Gets a value from the current `Page's` params set in front matter, with a fall back to the site param value. It will log an `ERROR` if the param with the given key could not be found in either.
+Gets a value from the current `Page's` params set in front matter, with a fallback to the site param value. It will log an `ERROR` if the param with the given key could not be found in either.
 
 ```bash
 {{</* param testparam */>}}
diff --git a/content/en/contribute/development.md b/content/en/contribute/development.md
index 1fa6a404b..a9d06343a 100644
--- a/content/en/contribute/development.md
+++ b/content/en/contribute/development.md
@@ -85,7 +85,7 @@ You will need to have Git installed on your computer to contribute to Hugo devel
 
 Git is a [version control system](https://en.wikipedia.org/wiki/Version_control) to track the changes of source code. Hugo depends on smaller third-party packages that are used to extend the functionality. We use them because we don't want to reinvent the wheel.
 
-Go ships with a sub-command called `get` that will download these packages for us when we setup our working environment. The source code of the packages is tracked with Git. `get` will interact with the Git servers of the package hosters in order to fetch all dependencies.
+Go ships with a sub-command called `get` that will download these packages for us when we set up our working environment. The source code of the packages is tracked with Git. `get` will interact with the Git servers of the package hosters in order to fetch all dependencies.
 
 Move back to the terminal and check if Git is already installed. Type in `git version` and press enter. You can skip the rest of this section if the command returned a version number. Otherwise [download](https://git-scm.com/downloads) the latest version of Git and follow this [installation guide](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
 
@@ -305,7 +305,7 @@ git log
 # Exit with q
 ```
 
-After making the last commit you may have forgot something. There is no need to create a new commit. Just add the latest changes and merge them into the intended commit:
+After making the last commit you may have forgotten something. There is no need to create a new commit. Just add the latest changes and merge them into the intended commit:
 
 ```txt
 git add --all
diff --git a/content/en/functions/GetPage.md b/content/en/functions/GetPage.md
index aa5e9323f..0c74e628b 100644
--- a/content/en/functions/GetPage.md
+++ b/content/en/functions/GetPage.md
@@ -46,7 +46,7 @@ And since `Page` also provides a `.GetPage` method, the above is the same as:
 
 ## .GetPage and Multilingual Sites
 
-The previous examples have used the full content filename to lookup the post. Depending on how you have organized your content (whether you have the language code in the file name or not, e.g. `my-post.en.md`), you may want to do the lookup without extension. This will get you the current language's version of the page:
+The previous examples have used the full content filename to look up the post. Depending on how you have organized your content (whether you have the language code in the file name or not, e.g. `my-post.en.md`), you may want to do the lookup without extension. This will get you the current language's version of the page:
 
 ```go-html-template
 {{ with .Site.GetPage "/blog/my-post" }}{{ .Title }}{{ end }}
diff --git a/content/en/functions/absurl.md b/content/en/functions/absurl.md
index 13524d2d6..808cc00d8 100644
--- a/content/en/functions/absurl.md
+++ b/content/en/functions/absurl.md
@@ -38,7 +38,7 @@ The last two examples may look strange but can be very useful. For example, the
 </script>
 {{< /code >}}
 
-The above uses the [apply function][] and also exposes how the Go template parser JSON-encodes objects inside `<script>` tags. See [the safeJS template function][safejs] for examples of how to tell Hugo not to escape strings inside of such tags.
+The above uses the [apply function][] and also exposes how the Go template parser JSON-encodes objects inside `<script>` tags. See [the safeJS template function][safejs] for examples of how to tell Hugo not to escape strings inside such tags.
 
 {{% note "Ending Slash" %}}
 `absURL` and `relURL` are smart about missing slashes, but they will *not* add a closing slash to a URL if it is not present.
diff --git a/content/en/functions/dict.md b/content/en/functions/dict.md
index 28d548b20..5c8ad9d8a 100644
--- a/content/en/functions/dict.md
+++ b/content/en/functions/dict.md
@@ -26,7 +26,7 @@ Note that the `key` can be either a `string` or a `string slice`. The latter is
 
 ## Example: Using `dict` to pass multiple values to a `partial`
 
-The partial below creates a SVG and expects `fill`, `height` and `width` from the caller:
+The partial below creates an SVG and expects `fill`, `height` and `width` from the caller:
 
 ### Partial definition
 
diff --git a/content/en/functions/intersect.md b/content/en/functions/intersect.md
index 2fe73ded8..8d4c50fe2 100644
--- a/content/en/functions/intersect.md
+++ b/content/en/functions/intersect.md
@@ -17,7 +17,7 @@ relatedfuncs: []
 deprecated: false
 aliases: []
 ---
-An useful example is to use it as `AND` filters when combined with where:
+A useful example is to use it as `AND` filters when combined with where:
 
 ## AND filter in where query
 
diff --git a/content/en/functions/partialCached.md b/content/en/functions/partialCached.md
index d7a70ac64..a0c317377 100644
--- a/content/en/functions/partialCached.md
+++ b/content/en/functions/partialCached.md
@@ -43,4 +43,4 @@ If you need to pass additional parameters to create unique variants, you can pas
 Note that the variant parameters are not made available to the underlying partial template. They are only use to create a unique cache key. Since Hugo `0.61.0` you can use any object as cache key(s), not just strings.
 
 
-> See also the [The Full Partial Series Part 1: Caching!](https://regisphilibert.com/blog/2019/12/hugo-partial-series-part-1-caching-with-partialcached/)
+> See also [The Full Partial Series Part 1: Caching!](https://regisphilibert.com/blog/2019/12/hugo-partial-series-part-1-caching-with-partialcached/)
diff --git a/content/en/functions/strings.HasSuffix.md b/content/en/functions/strings.HasSuffix.md
index 3b82ea055..78688a5cb 100644
--- a/content/en/functions/strings.HasSuffix.md
+++ b/content/en/functions/strings.HasSuffix.md
@@ -1,6 +1,6 @@
 ---
 title: strings.HasSuffix
-description: Determine whether or not a given string ends with the provided trailing suffix string.
+description: Determine whether a given string ends with the provided trailing suffix string.
 date: 2019-08-13
 publishdate: 2019-08-13
 lastmod: 2019-08-13
diff --git a/content/en/getting-started/configuration.md b/content/en/getting-started/configuration.md
index c8b94a94d..b8b21ed92 100644
--- a/content/en/getting-started/configuration.md
+++ b/content/en/getting-started/configuration.md
@@ -73,7 +73,7 @@ foo = "bar"
 │       └── params.toml
 ```
 
-Considering the structure above, when running `hugo --environment staging`, Hugo will use every settings from `config/_default` and merge `staging`'s on top of those.
+Considering the structure above, when running `hugo --environment staging`, Hugo will use every setting from `config/_default` and merge `staging`'s on top of those.
 
 Let's take an example to understand this better. Let's say you are using Google Analytics for your website. This requires you to specify `googleAnalytics = "G-XXXXXXXX"` in `config.toml`. Now consider the following scenario:
 - You don't want the Analytics code to be loaded in development i.e. in your `localhost`
@@ -388,7 +388,7 @@ Enable this to make all relative URLs relative to content root. Note that this d
 
 **Default value:** "ERROR"
 
-When using `ref` or `relref` to resolve page links and a link cannot resolved, it will be logged with this log level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).
+When using `ref` or `relref` to resolve page links and a link cannot be resolved, it will be logged with this log level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).
 
 ### refLinksNotFoundURL
 
@@ -508,7 +508,7 @@ useResourceCacheWhen
 writeStats {{< new-in "0.69.0" >}}
 : When enabled, a file named `hugo_stats.json` will be written to your project root with some aggregated data about the build, e.g. list of HTML entities published to be used to do [CSS pruning](/hugo-pipes/postprocess/#css-purging-with-postcss). If you're only using this for the production build, you should consider placing it below [config/production](/getting-started/configuration/#configuration-directory). It's also worth mentioning that, due to the nature of the partial server builds, new HTML entities will be added when you add or change them while the server is running, but the old values will not be removed until you restart the server or run a regular `hugo` build.
 
-**Note** that the prime use case for this is purging of unused CSS; it is build for speed and there may be false positives (e.g. elements that isn't really a HTML element).
+**Note** that the prime use case for this is purging of unused CSS; it is built for speed and there may be false positives (e.g., detection of HTML elements that are not HTML elements).
 
 noJSConfigInAssets {{< new-in "0.78.0" >}}
 : Turn off writing a `jsconfig.json` into your `/assets` folder with mapping of imports from running [js.Build](https://gohugo.io/hugo-pipes/js). This file is intended to help with intellisense/navigation inside code editors such as [VS Code](https://code.visualstudio.com/). Note that if you do not use `js.Build`, no file will be written.
@@ -533,7 +533,7 @@ Referrer-Policy = "strict-origin-when-cross-origin"
 Content-Security-Policy = "script-src localhost:1313"
 {{< /code-toggle >}}
 
-Since this is is "development only", it may make sense to put it below the `development` environment:
+Since this is "development only", it may make sense to put it below the `development` environment:
 
 
 {{< code-toggle file="config/development/server">}}
diff --git a/content/en/getting-started/installing.md b/content/en/getting-started/installing.md
index 1083f2c9a..0ac985558 100644
--- a/content/en/getting-started/installing.md
+++ b/content/en/getting-started/installing.md
@@ -111,7 +111,7 @@ scoop install hugo-extended
 
 #### Fetch from GitHub
 
-Since Hugo 0.48, Hugo uses the Go Modules support built into Go 1.11 to build. The easiest way to get started is to clone Hugo in a directory outside of the GOPATH, as in the following example:
+Since Hugo 0.48, Hugo uses the Go Modules support built into Go 1.11 to build. The easiest way to get started is to clone Hugo in a directory outside the GOPATH, as in the following example:
 
 {{< code file="from-gh.sh" >}}
 mkdir $HOME/src
diff --git a/content/en/hosting-and-deployment/hosting-on-azure-static-web-apps.md b/content/en/hosting-and-deployment/hosting-on-azure-static-web-apps.md
index 9d9daa578..cf06580e7 100644
--- a/content/en/hosting-and-deployment/hosting-on-azure-static-web-apps.md
+++ b/content/en/hosting-and-deployment/hosting-on-azure-static-web-apps.md
@@ -18,6 +18,6 @@ toc: true
 aliases: []
 ---
 
-You can create and deploy a Hugo web application to Azure Static Web Apps. The final result is a new Azure Static Web App with associated GitHub Actions that give you control over how the app is built and published. You'll learn how to create a Hugo app, setup an Azure Static Web App and deploy the Hugo app to Azure.
+You can create and deploy a Hugo web application to Azure Static Web Apps. The final result is a new Azure Static Web App with associated GitHub Actions that give you control over how the app is built and published. You'll learn how to create a Hugo app, set up an Azure Static Web App and deploy the Hugo app to Azure.
 
 Here's the tutorial on how to [Publish a Hugo site to Azure Static Web Apps](https://docs.microsoft.com/en-us/azure/static-web-apps/publish-hugo).
diff --git a/content/en/hosting-and-deployment/hosting-on-keycdn.md b/content/en/hosting-and-deployment/hosting-on-keycdn.md
index f3b880b9c..85a5ab5f4 100644
--- a/content/en/hosting-and-deployment/hosting-on-keycdn.md
+++ b/content/en/hosting-and-deployment/hosting-on-keycdn.md
@@ -1,7 +1,7 @@
 ---
 title: "Host on KeyCDN"
 date: 2017-09-12
-description: "Accelerate your Hugo site globally with a KeyCDN integration. This tutorial shows you how to setup your static site as a GitLab page behind a KeyCDN pull zone."
+description: "Accelerate your Hugo site globally with a KeyCDN integration. This tutorial shows you how to set up your static site as a GitLab page behind a KeyCDN pull zone."
 categories: [hosting and deployment]
 keywords: [keycdn,hosting,deployment,cdn]
 menu:
@@ -23,7 +23,7 @@ toc: false
 
 ## Create a KeyCDN Pull Zone
 
-The first step will be to login to your KeyCDN account and create a new zone. Name this whatever you like and select the [Pull Zone](https://www.keycdn.com/support/create-a-pull-zone/) option. As for the origin URL, your site will be running on [GitLab Pages](https://docs.gitlab.com/ee/user/project/pages/getting_started_part_one.html) with a URL of `https://youruser.gitlab.io/reponame/`. Use this as the Origin URL.
+The first step will be to log in to your KeyCDN account and create a new zone. Name this whatever you like and select the [Pull Zone](https://www.keycdn.com/support/create-a-pull-zone/) option. As for the origin URL, your site will be running on [GitLab Pages](https://docs.gitlab.com/ee/user/project/pages/getting_started_part_one.html) with a URL of `https://youruser.gitlab.io/reponame/`. Use this as the Origin URL.
 
 ![Screenshot of KeyCDN's pull zone creation page](/images/hosting-and-deployment/hosting-on-keycdn/keycdn-pull-zone.png)
 
diff --git a/content/en/hosting-and-deployment/hosting-on-netlify.md b/content/en/hosting-and-deployment/hosting-on-netlify.md
index 818e4a565..526795655 100644
--- a/content/en/hosting-and-deployment/hosting-on-netlify.md
+++ b/content/en/hosting-and-deployment/hosting-on-netlify.md
@@ -55,7 +55,7 @@ Select the repo you want to use for continuous deployment. If you have a large n
 
 ![Screenshot of step 1 of create a new site for Netlify: selecting the git provider](/images/hosting-and-deployment/hosting-on-netlify/netlify-create-new-site-step-2.jpg)
 
-Once selected, you'll be brought to a screen for basic setup. Here you can select the branch you wanted published, your [build command][], and your publish (i.e. deploy) directory. The publish directory should mirror that of what you've set in your [site configuration][config], the default of which is `public`. The following steps assume you are publishing from the `master` branch.
+Once selected, you'll be brought to a screen for basic setup. Here you can select the branch you want to publish, your [build command][], and your publish (i.e. deploy) directory. The publish directory should mirror that of what you've set in your [site configuration][config], the default of which is `public`. The following steps assume you are publishing from the `master` branch.
 
 ## Configure Hugo version in Netlify
 
diff --git a/content/en/hugo-pipes/babel.md b/content/en/hugo-pipes/babel.md
index 36d86c4d4..7071cb2c4 100755
--- a/content/en/hugo-pipes/babel.md
+++ b/content/en/hugo-pipes/babel.md
@@ -49,7 +49,7 @@ config [string]
 : Path to the Babel configuration file. Hugo will, by default, look for a `babel.config.js` in your project. More information on these configuration files can be found here: [babel configuration](https://babeljs.io/docs/en/configuration).
 
 minified [bool]
-: Save as much bytes as possible when printing
+: Save as many bytes as possible when printing
 
 noComments [bool]
 : Write comments to generated output (true by default)
diff --git a/content/en/hugo-pipes/introduction.md b/content/en/hugo-pipes/introduction.md
index f20b6427c..e7bb8ca50 100755
--- a/content/en/hugo-pipes/introduction.md
+++ b/content/en/hugo-pipes/introduction.md
@@ -127,7 +127,7 @@ Asset files must be stored in the asset directory. This is `/assets` by default,
 
 ### Asset Publishing
 
-Hugo publishes assets to the to the `publishDir` (typically `public`) when you invoke `.Permalink`, `.RelPermalink`, or `.Publish`. You can use `.Content` to inline the asset.
+Hugo publishes assets to the `publishDir` (typically `public`) when you invoke `.Permalink`, `.RelPermalink`, or `.Publish`. You can use `.Content` to inline the asset.
 
 ## Go Pipes
 
diff --git a/content/en/templates/data-templates.md b/content/en/templates/data-templates.md
index adf4f405e..3283b630a 100644
--- a/content/en/templates/data-templates.md
+++ b/content/en/templates/data-templates.md
@@ -210,7 +210,7 @@ To load local files with `getJSON` and `getCSV`, the source files must reside wi
 It applies the same output logic as above in [Get Remote Data](#get-remote-data).
 
 {{% note %}}
-The local CSV files to be loaded using `getCSV` must be located **outside** of the `data` directory.
+The local CSV files to be loaded using `getCSV` must be located **outside** the `data` directory.
 {{% /note %}}
 
 ## LiveReload with Data Files
diff --git a/content/en/templates/lists.md b/content/en/templates/lists.md
index 37c5dc976..18f03c6f1 100644
--- a/content/en/templates/lists.md
+++ b/content/en/templates/lists.md
@@ -544,7 +544,7 @@ While these are logical defaults, they are not always the desired order. There a
 
 ### Order Within Groups
 
-Because Grouping returns a `{{.Key}}` and a slice of pages, all of the ordering methods listed above are available.
+Because Grouping returns a `{{.Key}}` and a slice of pages, all the ordering methods listed above are available.
 
 Here is the ordering for the example that follows:
 
diff --git a/content/en/templates/menu-templates.md b/content/en/templates/menu-templates.md
index 65325b578..bdf89c2e5 100644
--- a/content/en/templates/menu-templates.md
+++ b/content/en/templates/menu-templates.md
@@ -20,8 +20,8 @@ toc: false
 ---
 
 Hugo makes no assumptions about how your rendered HTML will be
-structured. Instead, it provides all of the functions you will need to be
-able to build your menu however you want.
+structured. Instead, it provides all the functions you will need to
+build your menu however you want.
 
 The following is an example:
 
diff --git a/content/en/templates/output-formats.md b/content/en/templates/output-formats.md
index 44e697d34..eb8f6862f 100644
--- a/content/en/templates/output-formats.md
+++ b/content/en/templates/output-formats.md
@@ -233,7 +233,7 @@ A new output format needs a corresponding template in order to render anything u
 The key distinction for Hugo versions 0.20 and newer is that Hugo looks at an output format's `Name` and MediaType's `Suffixes` when choosing the template used to render a given `Page`.
 {{% /note %}}
 
-The following table shows examples of different output formats, the suffix used, and Hugo's respective template [lookup order][]. All of the examples in the table can:
+The following table shows examples of different output formats, the suffix used, and Hugo's respective template [lookup order][]. All the examples in the table can:
 
 * Use a [base template][base].
 * Include [partial templates][partials]
diff --git a/content/en/templates/shortcode-templates.md b/content/en/templates/shortcode-templates.md
index 5e6b1aff4..2b9070f2f 100644
--- a/content/en/templates/shortcode-templates.md
+++ b/content/en/templates/shortcode-templates.md
@@ -18,7 +18,7 @@ aliases: []
 toc: true
 ---
 
-Shortcodes are a means to consolidate templating into small, reusable snippets that you can embed directly inside of your content. In this sense, you can think of shortcodes as the intermediary between [page and list templates][templates] and [basic content files][].
+Shortcodes are a means to consolidate templating into small, reusable snippets that you can embed directly inside your content. In this sense, you can think of shortcodes as the intermediary between [page and list templates][templates] and [basic content files][].
 
 {{% note %}}
 Hugo also ships with built-in shortcodes for common use cases. (See [Content Management: Shortcodes](/content-management/shortcodes/).)
@@ -100,7 +100,7 @@ most helpful when the condition depends on either of the values, or both:
 
 #### `.Inner`
 
-If a closing shortcode is used, the `.Inner` variable will be populated with all of the content between the opening and closing shortcodes. If a closing shortcode is required, you can check the length of `.Inner` as an indicator of its existence.
+If a closing shortcode is used, the `.Inner` variable will be populated with the content between the opening and closing shortcodes. If a closing shortcode is required, you can check the length of `.Inner` as an indicator of its existence.
 
 A shortcode with content declared via the `.Inner` variable can also be declared without the content and without the closing by using the self-closing syntax:
 
diff --git a/content/en/templates/views.md b/content/en/templates/views.md
index 362f1ec62..495f701bd 100644
--- a/content/en/templates/views.md
+++ b/content/en/templates/views.md
@@ -63,7 +63,7 @@ The following is the [lookup order][lookup] for content views:
 
 ## Example: Content View Inside a List
 
-The following example demonstrates how to use content views inside of your [list templates][lists].
+The following example demonstrates how to use content views inside your [list templates][lists].
 
 ### `list.html`
 
diff --git a/content/en/tools/editors.md b/content/en/tools/editors.md
index e4fb9b44a..53b92016b 100644
--- a/content/en/tools/editors.md
+++ b/content/en/tools/editors.md
@@ -30,7 +30,7 @@ The Hugo community uses a wide range of preferred tools and has developed plug-i
 * [Hugo Helper](https://marketplace.visualstudio.com/items?itemName=rusnasonov.vscode-hugo). Hugo Helper is a plugin for Visual Studio Code that has some useful commands for Hugo. The source code can be found [here](https://github.com/rusnasonov/vscode-hugo).
 * [Hugo Language and Syntax Support](https://marketplace.visualstudio.com/items?itemName=budparr.language-hugo-vscode). Hugo Language and Syntax Support is a Visual Studio Code plugin for Hugo syntax highlighting and snippets. The source code can be found [here](https://github.com/budparr/language-hugo-vscode).
 * [Hugo Themer](https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-hugo-themer). Hugo Themer is an extension to help you while developing themes. It allows you to easily navigate through your theme files.
-* [Front Matter](https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-front-matter). Once you go for a static site, you need to think about how you are going to manage your articles. Front matter is a tool that helps you maintaining the metadata/front matter of your articles like: creation date, modified date, slug, tile, SEO check, and many more...
+* [Front Matter](https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-front-matter). Once you go for a static site, you need to think about how you are going to manage your articles. Front matter is a tool that helps you maintain the metadata/front matter of your articles like: creation date, modified date, slug, tile, SEO check, and many more...
 * [Syntax Highlighting for Hugo Shortcodes](https://github.com/kael-larkin/hugo-vscode-shortcode-syntax-highlighting). This extension add some syntax highlighting for Shortcodes, making visual identification of individual pieces easier.
 
 ## Emacs
diff --git a/content/en/variables/files.md b/content/en/variables/files.md
index d8f3daece..4e6c0632f 100644
--- a/content/en/variables/files.md
+++ b/content/en/variables/files.md
@@ -34,7 +34,7 @@ The `.File` object contains the following fields:
 : the filename without extension or optional language identifier (e.g., `foo`)
 
 .File.ContentBaseName
-: is a either TranslationBaseName or name of containing folder if file is a leaf bundle.
+: is either a TranslationBaseName or name of containing folder if file is a leaf bundle.
 
 .File.BaseFileName
 : the filename without extension (e.g., `foo.en`)
diff --git a/content/en/variables/site.md b/content/en/variables/site.md
index 1adaf3ac0..ff3275f0f 100644
--- a/content/en/variables/site.md
+++ b/content/en/variables/site.md
@@ -84,7 +84,7 @@ All the methods below, e.g. `.Site.RegularPages` can also be reached via the glo
 : a string representing the date/time of the most recent change to your site. This string is based on the [`date` variable in the front matter](/content-management/front-matter) of your content pages.
 
 .Site.Menus
-: all of the menus in the site.
+: all the menus in the site.
 
 .Site.Pages
 : array of all content ordered by Date with the newest first. This array contains only the pages in the current language. See [`.Site.Pages`]({{< relref "site.md#site-pages" >}}).