diff --git a/content/en/content-management/page-bundles.md b/content/en/content-management/page-bundles.md
index dc866445b..64b59194a 100644
--- a/content/en/content-management/page-bundles.md
+++ b/content/en/content-management/page-bundles.md
@@ -18,8 +18,8 @@ Page Bundles are a way to group [Page Resources](/content-management/page-resour
 
 A Page Bundle can be one of:
 
--   Leaf Bundle (leaf means it has no children)
--   Branch Bundle (home page, section, taxonomy terms, taxonomy list)
+- Leaf Bundle (leaf means it has no children)
+- Branch Bundle (home page, section, taxonomy terms, taxonomy list)
 
 |                                     | Leaf Bundle                                              | Branch Bundle                                                                                                                                                                                                      |
 |-------------------------------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------  |
diff --git a/content/en/content-management/syntax-highlighting.md b/content/en/content-management/syntax-highlighting.md
index c53a6d65e..0e5107f36 100644
--- a/content/en/content-management/syntax-highlighting.md
+++ b/content/en/content-management/syntax-highlighting.md
@@ -16,14 +16,12 @@ aliases: [/extras/highlighting/,/extras/highlight/,/tools/syntax-highlighting/]
 toc: true
 ---
 
-
 Hugo uses [Chroma](https://github.com/alecthomas/chroma) as its code highlighter; it is built in Go and is really, really fast -- and for the most important parts compatible with Pygments we used before.
 
 ## Configure Syntax Highlighter
 
 See [Configure Highlight](/getting-started/configuration-markup#highlight).
 
-
 ## Generate Syntax Highlighter CSS
 
 If you run with `pygmentsUseClasses=true` in your site config, you need a style sheet.
@@ -36,7 +34,6 @@ hugo gen chromastyles --style=monokai > syntax.css
 
 Run `hugo gen chromastyles -h` for more options. See https://xyproto.github.io/splash/docs/ for a gallery of available styles.
 
-
 ## Highlight Shortcode
 
 Highlighting is carried out via the [built-in shortcode](/content-management/shortcodes/) `highlight`. `highlight` takes exactly one required parameter for the programming language to be highlighted and requires a closing shortcode. Note that `highlight` is *not* used for client-side javascript highlighting.
@@ -80,8 +77,6 @@ func GetTitleFunc(style string) func(s string) string {
 }
 {{< / highlight >}}
 
-
-
 ## Highlight Template Func
 
 See [Highlight](/functions/highlight/).
diff --git a/content/en/contribute/themes.md b/content/en/contribute/themes.md
index 0fa7a68c1..fa22aedb2 100644
--- a/content/en/contribute/themes.md
+++ b/content/en/contribute/themes.md
@@ -24,9 +24,8 @@ A collection of all themes created by the Hugo community, including screenshots
 
 Another great site for Hugo themes is [jamstackthemes.dev/](https://jamstackthemes.dev/ssg/hugo/).
 
-
 ### Add Your Theme to the Repo
 
-In order to add your Hugo theme to [themes.gohugo.io] please [open up a new issue in the theme repository](https://github.com/gohugoio/hugoThemes/issues/new?template=theme-submission.md). **Please make sure that you've read the theme submission guidelines in the [README](https://github.com/gohugoio/hugoThemes/blob/master/README.md#adding-a-theme-to-the-list) of the hugoThemes repository.** 
+In order to add your Hugo theme to [themes.gohugo.io] please [open up a new issue in the theme repository](https://github.com/gohugoio/hugoThemes/issues/new?template=theme-submission.md). **Please make sure that you've read the theme submission guidelines in the [README](https://github.com/gohugoio/hugoThemes/blob/master/README.md#adding-a-theme-to-the-list) of the hugoThemes repository.**
 
 [themes.gohugo.io]: https://themes.gohugo.io/
diff --git a/content/en/hosting-and-deployment/hosting-on-bitbucket.md b/content/en/hosting-and-deployment/hosting-on-bitbucket.md
index 03710690e..9ab926751 100644
--- a/content/en/hosting-and-deployment/hosting-on-bitbucket.md
+++ b/content/en/hosting-and-deployment/hosting-on-bitbucket.md
@@ -56,11 +56,10 @@ In the rendered page response, the `https://__baseurl__` will be replaced with y
 
 We will now create a git repository and then push our code to Bitbucket. In Bitbucket, create a repository.
 
-![][1]
+![Bitbucket Screenshot][1]
 
 [1]: /images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-create-repo.png
 
-
 ```
 # initialize new git repository
 git init
@@ -133,11 +132,10 @@ Your code will be committed to Bitbucket, Bitbucket Pipelines will run your buil
 
 At this point, you can now create and edit blog posts directly in the Bitbucket UI.
 
-![][2]
+![Bitbucket blog Screenshot][2]
 
 [2]: /images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-blog-post.png
 
-
 ## Suggested next steps
 
 The code for this example can be found in this Bitbucket [repository](https://bitbucket.org/dundonian/hugo-docs-test). Aerobatic also provides a number of additional [plugins](https://www.aerobatic.com/docs) such as auth and redirects that you can use for your Hugo site.
diff --git a/content/en/hosting-and-deployment/hosting-on-keycdn.md b/content/en/hosting-and-deployment/hosting-on-keycdn.md
index ca4ba219b..8d9cb0e63 100644
--- a/content/en/hosting-and-deployment/hosting-on-keycdn.md
+++ b/content/en/hosting-and-deployment/hosting-on-keycdn.md
@@ -66,7 +66,7 @@ pages:
     - master
 
 ```
-Using this integration method,  you will have to specify the Zone ID and your [KeyCDN API](https://www.keycdn.com/api) key as secret variables. To do this, navigate to the top-left menu bar in GitLab and select Projects. Then, select your project and click on the Settings page. Finally, select Pipelines from the sub-menu and scroll down to the Secret Variable section. 
+Using this integration method,  you will have to specify the Zone ID and your [KeyCDN API](https://www.keycdn.com/api) key as secret variables. To do this, navigate to the top-left menu bar in GitLab and select Projects. Then, select your project and click on the Settings page. Finally, select Pipelines from the sub-menu and scroll down to the Secret Variable section.
 
 The Secret Variable for your Zone ID should look similar to:
 
@@ -89,6 +89,6 @@ git push -u origin master
 
 You can watch the progress and CI job output in your Gitlab project under “Pipelines”. 
 
-After verifying your CI job ran without issues, first check that your GitLab page shows up under `https://youruser.gitlab.io/reponame/` (it might look broken depending on your browser settings as all links point to your KeyCDN zone – don’t worry about that) and then by heading to whatever Zonealias / Zone URL you defined.
+After verifying your CI job ran without issues, first check that your GitLab page shows up under `https://youruser.gitlab.io/reponame/` (it might look broken depending on your browser settings as all links point to your KeyCDN zone – don’t worry about that) and then by heading to whatever Zone alias / Zone URL you defined.
 
 To learn more about Hugo hosting options with KeyCDN, check out the complete [Hugo hosting with KeyCDN integration guide](https://www.keycdn.com/support/hugo-hosting/).