Merge commit 'a024bc7d76fcc5e49e8210f9b0896db9ef21861a'

docs/content/en/hosting-and-deployment/_index.md

@@ -1,7 +1,7 @@
 ---
 title: Hosting and deployment
-linkTitle: In this section
-description: Site builds, automated deployments, and popular hosting solutions.
+
+description: Services and tools to host and deploy your site.
 categories: []
 keywords: []
 menu:
@@ -9,7 +9,7 @@ menu:
     identifier: hosting-and-deployment-in-this-section
     parent: hosting-and-deployment
     weight: 1
-weight: 1
+weight: 10
 ---
 
 Because Hugo renders *static* websites, you can host your new Hugo website virtually anywhere. The following represent only a few of the more popular hosting and automated deployment solutions used by the Hugo community.

docs/content/en/hosting-and-deployment/hosting-on-github/index.md

@@ -188,7 +188,7 @@ The example workflow above includes this step, which typically takes 10‑15
 
 You may remove this step if your site, themes, and modules do not transpile Sass to CSS using the [Dart Sass] transpiler.
 
-[Dart Sass]: /hugo-pipes/transpile-sass-to-css/#dart-sass
+[Dart Sass]: /functions/css/sass/#dart-sass
 
 ## Other resources
 

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

@@ -20,7 +20,7 @@ menu:
 
 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)
+![Screenshot of KeyCDN's pull zone creation page](keycdn-pull-zone.png)
 
 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.
 
@@ -64,17 +64,17 @@ Using this integration method,  you will have to specify the Zone ID and your [K
 
 The Secret Variable for your Zone ID should look similar to:
 
-![Screenshot of setting the Zone ID secret variable](/images/hosting-and-deployment/hosting-on-keycdn/secret-zone-id.png)
+![Screenshot of setting the Zone ID secret variable](secret-zone-id.png)
 
 While the Secret Variable for your API Key will look similar to:
 
-![Screenshot of setting the API Key secret variable](/images/hosting-and-deployment/hosting-on-keycdn/secret-api-key.png)
+![Screenshot of setting the API Key secret variable](secret-api-key.png)
 
 The Zone ID and API key are used to purge your zone – it’s not strictly needed but otherwise, the CDN might deliver older versions of your assets for quite a while.
 
 ## Push your changes to GitLab
 
-Now it’s time to push the newly created repository to GitLab:
+Now it's time to push the newly created repository to GitLab:
 
 ```sh
 git remote add origin git@gitlab.com:youruser/ci-example.git