Merge commit '35dec7c96f7ee3eb17dd444f7067f0c776fb56ae'

15 files changed, 32 insertions, 40 deletions

diff --git a/docs/content/en/showcase/1password-support/bio.md b/docs/content/en/showcase/1password-support/bio.md
index 9187908d9..3e15adc9f 100644
--- a/docs/content/en/showcase/1password-support/bio.md
+++ b/docs/content/en/showcase/1password-support/bio.md
@@ -1,5 +1,4 @@
 
 **1Password** is a password manager that keeps you safe online. It protects your secure information behind the one password only you know.
 
-
 The [1Password Support](https://support.1password.com/) website was built from scratch with **Hugo** and enhanced with **React** and **Elasticsearch** to give us the best of both worlds: The simplicity and performance of a static site, with the richness of a hosted web app.
diff --git a/docs/content/en/showcase/1password-support/index.md b/docs/content/en/showcase/1password-support/index.md
index 2bcbff3fd..ed44053c8 100644
--- a/docs/content/en/showcase/1password-support/index.md
+++ b/docs/content/en/showcase/1password-support/index.md
@@ -34,6 +34,6 @@ Finding a tool that will make your customers, writers, designers, _and_ DevOps t
 * [1Password Support](https://support.1password.com) uses Hugo with a custom theme. It shares styles and some template code with [1Password.com](https://1password.com), which we also moved to Hugo in 2016.
 * Code and articles live in a private GitHub repository, which is deployed to a static content server using Git hooks.
 * Writers build and preview the site on their computers and contribute content using pull requests.
- * We use Hugo's [multilingual support](/content-management/multilingual/) to build the site in English, Spanish, French, Italian, German, and Russian. With the help of Hugo, 1Password Support became our very first site in multiple languages.
+* We use Hugo's [multilingual support](/content-management/multilingual/) to build the site in English, Spanish, French, Italian, German, and Russian. With the help of Hugo, 1Password Support became our very first site in multiple languages.
 * Our [contact form](https://support.1password.com/contact) is a single-page React app. We were able to integrate it with Hugo seamlessly thanks to its support for static files.
 * The one part of the support site which is not static is our search engine, which we developed with Elasticsearch and host on AWS.
diff --git a/docs/content/en/showcase/alora-labs/bio.md b/docs/content/en/showcase/alora-labs/bio.md
index d304cf191..f14a90b75 100644
--- a/docs/content/en/showcase/alora-labs/bio.md
+++ b/docs/content/en/showcase/alora-labs/bio.md
@@ -1,3 +1,3 @@
-**Alora Labs** is a product development consultancy headquartered in Toronto, Canada. 
+**Alora Labs** is a product development consultancy headquartered in Toronto, Canada.
 
 We help companies build software and IoT products and were recently recognized as one of the [**top IoT development firms**](https://aloralabs.com/insights/alora-labs-receives-clutch-2021-top-iot-agency-award) in Toronto.
diff --git a/docs/content/en/showcase/alora-labs/index.md b/docs/content/en/showcase/alora-labs/index.md
index 5e6e18131..559169319 100644
--- a/docs/content/en/showcase/alora-labs/index.md
+++ b/docs/content/en/showcase/alora-labs/index.md
@@ -9,10 +9,10 @@ aliases: [/showcase/aloralabs/]
 
 At Alora Labs we always have an eye open for new tools and technology that we can utilize to the benefit of our customers or internal projects like our website.
 
-The previous iteration of our site was built with Jekyll, which served us well at first. However as time went on, we became frustrated with the number of dependencies we had to rely on, that would often break at the most inconvenient times. 
+The previous iteration of our site was built with Jekyll, which served us well at first. However as time went on, we became frustrated with the number of dependencies we had to rely on, that would often break at the most inconvenient times.
 
 Hugo was a breath of fresh air in this regard, a single binary that works equally well on Windows as it did on macOS or Linux. We no longer need additional tools for image optimization, Sass compilation or JavaScript bundling. Everything just works, and with a substantial performance boost too.
 
-Hugo has become a favorite tool in the toolbelt and the foundation for many client projects. We couldn't be happier with the switch and we are optimistic about recommending Hugo for many years to come. 
+Hugo has become a favorite tool in the tool belt and the foundation for many client projects. We couldn't be happier with the switch and we are optimistic about recommending Hugo for many years to come.
 
-Thank you to the vibrant community and talented development team for all the hard work in making Hugo a success. As excellent as Hugo is now, we cannot wait to see what the release notes have in store for us next.
\ No newline at end of file
+Thank you to the vibrant community and talented development team for all the hard work in making Hugo a success. As excellent as Hugo is now, we cannot wait to see what the release notes have in store for us next.
diff --git a/docs/content/en/showcase/ampio-help/index.md b/docs/content/en/showcase/ampio-help/index.md
index 3d21192b8..2daafbbe1 100644
--- a/docs/content/en/showcase/ampio-help/index.md
+++ b/docs/content/en/showcase/ampio-help/index.md
@@ -33,7 +33,7 @@ The turning point was the introduction of a new key requirement---each document
 
 On top of that new development, we had to remember another one of our key requirements, namely, that mostly non-programmers were to be responsible for the service maintenance and content creation. Initially, we were leaning towards headless CMS-based solutions, but finally we made a bold move and decided to create a Git-managed Jamstack service and see what happens.
 
-## Hugo to the rescue!
+## Hugo to the rescue
 
 Hugo was our first choice of SSG. The multilingualism support was the primary feature that convinced us. Later on, going through the documentation, we continued to discover new exciting features that we didn't even know we needed when we started.
 
@@ -47,7 +47,7 @@ We even implemented a simple REST API generated by Hugo! We have yet to find som
 
 When talking about Hugo, we cannot forget about the speed. At the beginning we were not considering it a killer feature, but as our document base grew bigger, we appreciated it more and more. Dry-runs are not so common---most of the time we are working on one of the documents with cache already built during one of the previous Hugo runs. In such a scenario, Hugo rebuilds the site in about a second and we consider it a very good result.
 
-```
+```text
                    | EN  | PL
 -------------------+-----+------
   Pages            | 483 | 486
diff --git a/docs/content/en/showcase/bypasscensorship/bio.md b/docs/content/en/showcase/bypasscensorship/bio.md
index 6563e13ca..0a847df1e 100644
--- a/docs/content/en/showcase/bypasscensorship/bio.md
+++ b/docs/content/en/showcase/bypasscensorship/bio.md
@@ -3,4 +3,4 @@ Bypass Censorship find and promote tools that provide Internet access to everyon
 The site is built by:
 
 * [Leyla Avsar](https://www.leylaavsar.com/) (designer)
-* [Fredrik Jonsson](https://xdeb.net/) (dev)
\ No newline at end of file
+* [Fredrik Jonsson](https://xdeb.net/) (dev)
diff --git a/docs/content/en/showcase/bypasscensorship/index.md b/docs/content/en/showcase/bypasscensorship/index.md
index a266797ea..8cbda9aa6 100644
--- a/docs/content/en/showcase/bypasscensorship/index.md
+++ b/docs/content/en/showcase/bypasscensorship/index.md
@@ -21,4 +21,4 @@ It's a simply site, basically one page in seven languages. I had no problems get
 
 Thanks to the design by [Leyla Avsar](https://www.leylaavsar.com/) the site also looks good. I used the [Hugo Zen theme](https://github.com/frjo/hugo-theme-zen) with a few custom templates and the needed CSS.
 
-The editors can maintain content via [Forestry.io CMS](https://forestry.io/) or directly via Git. Forestry does unfortunately not have multilingual support. All the language versions are in one pile making it harder to find the right file to edit, but it works.
\ No newline at end of file
+The editors can maintain content via [Forestry.io CMS](https://forestry.io/) or directly via Git. Forestry does unfortunately not have multilingual support. All the language versions are in one pile making it harder to find the right file to edit, but it works.
diff --git a/docs/content/en/showcase/digitalgov/index.md b/docs/content/en/showcase/digitalgov/index.md
index c0a927edb..4376bbf03 100644
--- a/docs/content/en/showcase/digitalgov/index.md
+++ b/docs/content/en/showcase/digitalgov/index.md
@@ -12,11 +12,11 @@ Through collaboration in our communities of practice, Digital.gov is a window in
 
 Digital.gov is built using the [U.S. Web Design System](https://designsystem.digital.gov/) (USWDS) and have followed the [design principles](https://designsystem.digital.gov/maturity-model/) in building out our new site:
 
--   **Start with real user needs**  — We used human-centered design methods to inform our product decisions (like qualitative user research), and gathered feedback from real users. We also continually test our assumptions with small experiments.
--   **Earn trust**  —We recognize that trust has to be earned every time. We are including all  [required links and content](https://digital.gov/resources/required-web-content-and-links/)  on our site, clearly identifying as a government site, building with modern best practices, and using HTTPS.
--   **Embrace accessibility**  —  [Accessibility](https://digital.gov/resources/intro-accessibility/)  affects everybody, and we built it into every decision. We’re continually working to conform to Section 508 requirements, use user experience best practices, and support a wide range of devices.
--   **Promote continuity**  — We started from shared solutions like USWDS and  [Federalist](https://federalist.18f.gov/). We designed our site to clearly identify as a government site by including USWDS’s .gov banner, common colors and patterns, and built with modern best practices.
--   **Listen**  — We actively collect user feedback and web metrics. We use the  [Digital Analytics Program](https://digital.gov/services/dap/)  (DAP) and analyze the data to discover actionable insights. We make small, incremental changes to continuously improve our website by listening to readers and learning from what we hear.
+- **Start with real user needs**  — We used human-centered design methods to inform our product decisions (like qualitative user research), and gathered feedback from real users. We also continually test our assumptions with small experiments.
+- **Earn trust**  —We recognize that trust has to be earned every time. We are including all  [required links and content](https://digital.gov/resources/required-web-content-and-links/)  on our site, clearly identifying as a government site, building with modern best practices, and using HTTPS.
+- **Embrace accessibility**  —  [Accessibility](https://digital.gov/resources/intro-accessibility/)  affects everybody, and we built it into every decision. We’re continually working to conform to Section 508 requirements, use user experience best practices, and support a wide range of devices.
+- **Promote continuity**  — We started from shared solutions like USWDS and  [Federalist](https://federalist.18f.gov/). We designed our site to clearly identify as a government site by including USWDS’s .gov banner, common colors and patterns, and built with modern best practices.
+- **Listen**  — We actively collect user feedback and web metrics. We use the  [Digital Analytics Program](https://digital.gov/services/dap/)  (DAP) and analyze the data to discover actionable insights. We make small, incremental changes to continuously improve our website by listening to readers and learning from what we hear.
 
 _More on the [USWDS maturity model »](https://designsystem.digital.gov/maturity-model/)_
 
@@ -34,7 +34,7 @@ At the moment, it takes around `32 seconds` to build close to `~10,000` pages!
 
 Take a look:
 
-```bash
+```text
 
                    |  EN
 -------------------+-------
@@ -48,19 +48,17 @@ Take a look:
   Cleaned          |    0
 
 Built in 32.427 seconds
-
 ```
 
 In addition to Hugo, we are proudly using a number of other tools and services, all built by government are free to use:
 
--   [Federalist](https://federalist.18f.gov/)
--   [Search.gov](https://www.search.gov/)  — A free, hosted search platform for federal websites.
--   [Cloud.gov](https://www.cloud.gov/)  — helps teams build, run, and authorize cloud-ready or legacy government systems quickly and cheaply.
--   [Federal CrowdSource Mobile Testing Program](https://digital.gov/services/mobile-application-testing-program/)  — Free mobile compatibility testing by feds, for feds.
--   [Digital Analytics Program](https://digital.gov/services/dap/)  (DAP) — A free analytics tool for measuring digital services in the federal government
--   [Section508.gov](https://www.section508.gov/)  and  [PlainLanguage.gov](https://www.plainlanguage.gov/)  resources
--   [API.data.gov](https://api.data.gov/)  — a free API management service for federal agencies
--   [U.S. Digital Registry](https://digital.gov/services/u-s-digital-registry/)  — A resource for confirming the official status of government social media accounts, mobile apps, and mobile websites.
-
+- [Federalist](https://federalist.18f.gov/)
+- [Search.gov](https://www.search.gov/)  — A free, hosted search platform for federal websites.
+- [Cloud.gov](https://www.cloud.gov/)  — helps teams build, run, and authorize cloud-ready or legacy government systems quickly and cheaply.
+- [Federal CrowdSource Mobile Testing Program](https://digital.gov/services/mobile-application-testing-program/)  — Free mobile compatibility testing by feds, for feds.
+- [Digital Analytics Program](https://digital.gov/services/dap/)  (DAP) — A free analytics tool for measuring digital services in the federal government
+- [Section508.gov](https://www.section508.gov/)  and  [PlainLanguage.gov](https://www.plainlanguage.gov/)  resources
+- [API.data.gov](https://api.data.gov/)  — a free API management service for federal agencies
+- [U.S. Digital Registry](https://digital.gov/services/u-s-digital-registry/)  — A resource for confirming the official status of government social media accounts, mobile apps, and mobile websites.
 
 **Questions or feedback?** [Submit an issue](https://github.com/GSA/digitalgov.gov/issues) or send us an email to [digitalgov@gsa.gov](mailto:digitalgov@gsa.gov) :heart:
diff --git a/docs/content/en/showcase/forestry/index.md b/docs/content/en/showcase/forestry/index.md
index fbfe9b961..32a932a7a 100644
--- a/docs/content/en/showcase/forestry/index.md
+++ b/docs/content/en/showcase/forestry/index.md
@@ -14,7 +14,7 @@ In our early research we looked at Ionic’s [site](https://github.com/ionic-tea
 
 We knew Hugo was fast but we did [some additional benchmarking](https://forestry.io/blog/hugo-vs-jekyll-benchmark/) before making our decision. Seeing Hugo in action is a whole different world of awesome. Hugo takes less than one second to build our 150-page site! Take a look:
 
-```bash
+```text
                    | EN   
 +------------------+-----+
   Pages            | 141  
@@ -41,7 +41,7 @@ Lastly, we want to take the opportunity to give some love to other amazing tools
 * Chris can’t think of modern web development without [**Gulp**](https://gulpjs.com/) & [**Webpack**](https://webpack.js.org/). We used them to add additional build steps such as Browsersync, CSS, JS and SVG optimization.
 * Speaking about adding steps to our build, our lives would be much harder without [**CircleCI**](https://circleci.com/) for continuous deployment and automated testing purposes.
 * We can’t stop raving about [**Algolia**](https://www.algolia.com/). Chris loves it and even wrote a tutorial on [how to implement Algolia](https://forestry.io/blog/search-with-algolia-in-hugo/) into static sites using Hugo’s [Custom Outputs](/templates/output-formats/).
-*  [**Cloudinary**](https://cloudinary.com/) is probably one of the easiest ways to get responsive images into your website.
+* [**Cloudinary**](https://cloudinary.com/) is probably one of the easiest ways to get responsive images into your website.
 * We might be a little biased on this one - We think [**Forestry.io**](https://forestry.io/) is a great way to add a content management system with a clean UI on top of your site without interrupting your experience as a developer.
 * For hosting purposes we use the almighty [**AWS**](https://aws.amazon.com/).
 * [**Formspree.io**](https://formspree.io/) is managing our support and enterprise requests.
diff --git a/docs/content/en/showcase/godot-tutorials/index.md b/docs/content/en/showcase/godot-tutorials/index.md
index 56a8dfc4d..3b71fd8bc 100644
--- a/docs/content/en/showcase/godot-tutorials/index.md
+++ b/docs/content/en/showcase/godot-tutorials/index.md
@@ -13,7 +13,6 @@ byline: "[Godot Tutorials](https://godottutorials.com), Web Developer & Game Pro
 
 ---
 
-
 [Godot Tutorials](https://godottutorials.com) started as a way to teach beginners game programming and game development.
 As I created videos, I ran into a problem; if I made a mistake with a YouTube video, it was difficult to correct errors.
 
@@ -22,4 +21,4 @@ I discovered that blogging episodes and having articles that teach on top of my
 As I researched blogging platforms, I came across two solutions; however, I chose [Hugo](https://gohugo.io) because it's built with Markdown in mind and simplified my workflow.
 
 In a sense, with [Hugo](https://gohugo.io) programmed the right way, I can focus **more time on planning, creating, and editing**
-my videos and **less time maintaining and fixing** my website.
\ No newline at end of file
+my videos and **less time maintaining and fixing** my website.
diff --git a/docs/content/en/showcase/hartwell-insurance/index.md b/docs/content/en/showcase/hartwell-insurance/index.md
index 66fc46f44..ef0587e41 100644
--- a/docs/content/en/showcase/hartwell-insurance/index.md
+++ b/docs/content/en/showcase/hartwell-insurance/index.md
@@ -62,7 +62,7 @@ The most encouraging result is how quick the site is around the world. Most Toma
 
 ---
 
-This project was such a blast to develop, it’s a real pleasure to put new technologies to good use in production, and to see real performance and usability benefits from them. Even using classic web methods of serving folders with files is fun when you’ve been databasing for a while – there’s something really ‘pure’ about it.
+This project was such a blast to develop, it’s a real pleasure to put new technologies to good use in production, and to see real performance and usability benefits from them. Even using classic web methods of serving folders with files is fun when you’ve been using dynamic systems for a while – there’s something really pure about it.
 
 ---
 
diff --git a/docs/content/en/showcase/letsencrypt/index.md b/docs/content/en/showcase/letsencrypt/index.md
index 18221ed68..6ad4b7840 100644
--- a/docs/content/en/showcase/letsencrypt/index.md
+++ b/docs/content/en/showcase/letsencrypt/index.md
@@ -17,5 +17,4 @@ That site is bookmarked in many browsers, so preserving the URLs was a must. Hug
 
 The lessons learned from this also lead to [disableLanguages](/content-management/multilingual/#disable-a-language) in Hugo `0.34` (a way to turn off languages during translation). And I also registered [this issue](https://github.com/gohugoio/hugo/issues/4463). Once fixed it will make it easier to handle partially translated sites.
 
-
 [^1]: The work on getting the content translated is in progress.
diff --git a/docs/content/en/showcase/pharmaseal/index.md b/docs/content/en/showcase/pharmaseal/index.md
index 64e9960a3..d324833c9 100644
--- a/docs/content/en/showcase/pharmaseal/index.md
+++ b/docs/content/en/showcase/pharmaseal/index.md
@@ -11,20 +11,18 @@ siteURL: https://pharmaseal.co/
 # Link to the site's Hugo source code if public and you can/want to share.
 # Remove or leave blank if not needed/wanted.
 
-
 # Add credit to the article author. Leave blank or remove if not needed/wanted.
 byline: "[Roboto Studio](https://roboto.studio), Jonathan Alford"
 
 ---
 
-
 We wanted to shake the status quo with PHARMASEAL, opting for a fast and scalable website built with Hugo instead of slower monolithic systems the competitors were using.
 
 We had two goals:
 
 **Make it fast**
 
-We wanted to optimise the site as much as possible, so we opted for using Cloudinary, enabling us to take advantage of on-the-fly image manipulation, and thanks to the sheer speed of static sites, we achieved a perfect optimisation score with Google audits.
+We wanted to optimize the site as much as possible, so we opted for using Cloudinary, enabling us to take advantage of on-the-fly image manipulation, and thanks to the sheer speed of static sites, we achieved a perfect optimization score with Google audits.
 
 Because we're hosting the site through Netlify and our target audience is in America, we are taking advantage of Netlify edge (Their alternative to a CDN). We're talking blazing fast.
 
@@ -34,4 +32,4 @@ We're big fans of simplicity, and that's what we delivered with the Forestry bui
 
 PHARMASEAL have found Forestry CMS combined with HUGO to be so effective at producing fast, purpose driven pages, that we have worked with them to add even more blocks in a scalable, modular fashion.
 
-**TLDR:** We're blown away with HUGO, the sheer speed, scalability and deployment possibilities with Netlify is the 💣
\ No newline at end of file
+**TLDR:** We're blown away with HUGO, the sheer speed, scalability and deployment possibilities with Netlify is the 💣
diff --git a/docs/content/en/showcase/quiply-employee-communications-app/bio.md b/docs/content/en/showcase/quiply-employee-communications-app/bio.md
index f72a62554..f79677a1a 100644
--- a/docs/content/en/showcase/quiply-employee-communications-app/bio.md
+++ b/docs/content/en/showcase/quiply-employee-communications-app/bio.md
@@ -1,4 +1,4 @@
 **Quiply** is an employee communications app enabling mobile collaboration across an entire organization.
-Our customers get their own branded app enabling them to communicate fast and effectively with all employees, also non-desk and shift workers. 
+Our customers get their own branded app enabling them to communicate fast and effectively with all employees, also non-desk and shift workers.
 
 As the Quiply app's build process is based on **Gulp**, we have started to build our company and product website using **Gulp + Hugo** which is super-fast and gives us exactly the flexibility we need.
diff --git a/docs/content/en/showcase/template/bio.md b/docs/content/en/showcase/template/bio.md
index 597163340..de9287898 100644
--- a/docs/content/en/showcase/template/bio.md
+++ b/docs/content/en/showcase/template/bio.md
@@ -3,6 +3,5 @@ Add some **general info** about the site here.
 
 The site is built by:
 
-* [Person 1](https://example.com)
-* [Person 1](https://example.com)
-
+* [Person 1](https://example.org)
+* [Person 1](https://example.org)