Fixing typos, whitespace issues and links

content/en/commands/hugo_mod_get.md

@@ -18,7 +18,7 @@ Some examples:
 Install the latest version possible for a given module:
 
     hugo mod get github.com/gohugoio/testshortcodes
-    
+
 Install a specific version:
 
     hugo mod get github.com/gohugoio/testshortcodes@v0.3.0

content/en/content-management/comments.md

@@ -56,7 +56,7 @@ There are a few alternatives to commenting on static sites for those who do not
 * [IntenseDebate](https://intensedebate.com/)
 * [Graph Comment][]
 * [Muut](https://muut.com/)
-* [isso](https://posativ.org/isso/) (Self-hosted, Python)
+* [Isso](https://posativ.org/isso/) (Self-hosted, Python)
     * [Tutorial on Implementing Isso with Hugo][issotutorial]
 * [Utterances](https://utteranc.es/) (Open source, GitHub comments widget built on GitHub issues)
 * [Remark](https://github.com/umputun/remark) (Open source, Golang, Easy to run docker)

content/en/hosting-and-deployment/hosting-on-keycdn.md

@@ -24,13 +24,13 @@ draft: 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 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.
 
-![Screenshot of KeyCDN's pull zone creation page](/images/hosting-and-deployment/hosting-on-keycdn/keycdn-pull-zone.png) 
+![Screenshot of KeyCDN's pull zone creation page](/images/hosting-and-deployment/hosting-on-keycdn/keycdn-pull-zone.png)
 
-While the origin location doesn’t exist yet, you will need to use your new Zone URL address (or [Zonealias](https://www.keycdn.com/support/create-a-zonealias/)) in the `.gitlab-ci.yml` file that will be uploaded to your GitLab project. 
+While the origin location doesn’t exist yet, you will need to use your new Zone URL address (or [Zone Alias](https://www.keycdn.com/support/create-a-zone-alias/)) in the `.gitlab-ci.yml` file that will be uploaded to your GitLab project.
 
-Ensure that you use your Zone URL or Zonealias as the `BASEURL` variable in the example below. This will be the user-visible website address.
+Ensure that you use your Zone URL or Zone alias as the `BASEURL` variable in the example below. This will be the user-visible website address.
 
 ## Configure Your .gitlab-ci.yml File
 

content/en/hugo-modules/configuration.md

@@ -58,7 +58,7 @@ Any of the above can be omitted.
 min
 : The minimum Hugo version supported, e.g. `0.55.0`
 
-max 
+max
 : The maximum Hugo version supported, e.g. `0.55.0`
 
 extended
@@ -73,7 +73,7 @@ extended
   ignoreConfig = false
   disable = false
 [[module.imports]]
-  path = "my-shortcodes"  
+  path = "my-shortcodes"
 {{< /code-toggle >}}
 
 path

content/en/hugo-modules/use-modules.md

@@ -36,7 +36,7 @@ Also see the [CLI Doc](/commands/hugo_mod_init/).
 The easiest way to use a Module for a theme is to import it in the config.
 
 1. Initialize the hugo module system: `hugo mod init github.com/<your_user>/<your_project>`
-2. Import the theme in your `config.toml`: 
+2. Import the theme in your `config.toml`:
 
 ```toml
 [module]
@@ -87,7 +87,7 @@ One way to do local development of a module imported in a project is to add a re
 replace github.com/bep/hugotestmods/mypartials => /Users/bep/hugotestmods/mypartials
 ```
 
-If you have the `hugo server` running, the configuration will be reloaded and `/Users/bep/hugotestmods/mypartials` put on the watch list. 
+If you have the `hugo server` running, the configuration will be reloaded and `/Users/bep/hugotestmods/mypartials` put on the watch list.
 
 
 ## Print Dependency Graph
@@ -114,7 +114,7 @@ Also see the [CLI Doc](/commands/hugo_mod_graph/).
 
 ## Vendor Your Modules
 
-`hugo mod vendor` will write all the module depencies to a `_vendor` folder, which will then be used for all subsequent builds.
+`hugo mod vendor` will write all the module dependencies to a `_vendor` folder, which will then be used for all subsequent builds.
 
 Note that:
 

content/en/showcase/fireship/index.md

@@ -1,5 +1,4 @@
 ---
-
 title: fireship.io
 date: 2019-02-02
 description: "Showcase: \"Hugo helps us create complex technical content that integrates engaging web components\""
@@ -10,9 +9,9 @@ byline: "[Jeff Delaney](https://github.com/codediodeio), Fireship.io Creator"
 
 After careful consideration of JavaScript/JSX-based static site generators, it became clear that Hugo was the only tool capable of handling our project's complex demands. Not only do we have multiple content formats and taxonomies, but we often need to customize the experience at a more granular level. The problems Hugo has solved for us include:
 
-- **Render speed.** We know from past experience that JavaScript-based static site generators become very slow when you have thousands of pages and images. 
-- **Feature-rich.** Our site has a long list of specialized needs and Hugo somehow manages to cover every single use case. 
-- **Composability.** Hugo's partial and shortcode systems empower us to write DRY and maintainable templates.  
-- **Simplicity.** Hugo is easy to learn (even without Go experience) and doesn't burden us with brittle dependencies. 
+- **Render speed.** We know from past experience that JavaScript-based static site generators become very slow when you have thousands of pages and images.
+- **Feature-rich.** Our site has a long list of specialized needs and Hugo somehow manages to cover every single use case.
+- **Composability.** Hugo's partial and shortcode systems empower us to write DRY and maintainable templates.
+- **Simplicity.** Hugo is easy to learn (even without Go experience) and doesn't burden us with brittle dependencies.
 
-The site is able to achieve Lighthouse performance scores of 95+, despite the fact that it is a fully interactive PWA that ships Angular and Firebase in the JS bundle. This is made possible by (1) prerendering content with Hugo and (2) lazily embedding native web components directly in the HTML and markdown. We provide a [detailed explanation](https://youtu.be/gun8OiGtlNc) of the architecture on YouTube and can't imagine development without Hugo. 
+The site is able to achieve Lighthouse performance scores of 95+, despite the fact that it is a fully interactive PWA that ships Angular and Firebase in the JS bundle. This is made possible by (1) prerendering content with Hugo and (2) lazily embedding native web components directly in the HTML and markdown. We provide a [detailed explanation](https://youtu.be/gun8OiGtlNc) of the architecture on YouTube and can't imagine development without Hugo.

content/en/showcase/hapticmedia/index.md

@@ -15,7 +15,7 @@ Hugo addresses all these needs, coupled with [Forestry.io](https://forestry.io/)
 
 
 ## What we liked
-- The **multilingual** content support, especially simpel to setup.
+- The **multilingual** content support, especially simple to setup.
 - The **multiple environments** support (develop, staging, test, production, ...).
 - Although a hard start with the Go language, the power of the **Hugo's templating**.
 - The **partial layouts**, including the `internals` (e.g. social metas).

content/en/showcase/linode/index.md

@@ -1,15 +1,9 @@
 ---
-
 title: Linode Docs
-
 date: 2018-02-12
-
 description: "Showcase: \"Hugo allows us to build thousands of pages in seconds.\""
-
 siteURL: https://linode.com/docs/
-
 siteSource: https://github.com/linode/docs
-
 ---
 
 The documentation team at Linode has been writing guides since 2009, with the goal of helping new and experienced Linux users find the best tools and get the most out of their systems.