Merge commit 'cb39847dee488c373dd5bc2a3706385342a59355'

docs/content/en/hosting-and-deployment/deployment-with-wercker.md

@@ -289,8 +289,6 @@ Once this workflow is established, you can update your website automatically by
 
 [The source code for the site used in this guide is available on GitHub][guidesource], as is the [Wercker Hugo Build step][guidestep].
 
-If you want to see an example of how you can deploy to S3 instead of GitHub pages, check [Wercker's documentation][werckerdocs] for guidance on setup.
-
 [1]: /images/hosting-and-deployment/deployment-with-wercker/creating-a-basic-hugo-site.png
 [2]: /images/hosting-and-deployment/deployment-with-wercker/adding-the-project-to-github.png
 [3]: /images/hosting-and-deployment/deployment-with-wercker/wercker-sign-up.png
@@ -321,4 +319,3 @@ If you want to see an example of how you can deploy to S3 instead of GitHub page
 [hugoconfig]: /getting-started/configuration/
 [publicappurl]: https://app.wercker.com/#applications/5586dcbdaf7de9c51b02b0d5
 [quickstart]: /getting-started/quick-start/
-[werckerdocs]: http://devcenter.wercker.com/docs/deploy/s3.html

docs/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.

docs/content/en/hosting-and-deployment/hosting-on-gitlab.md

@@ -77,6 +77,10 @@ That's it! You can now follow the CI agent building your page at `https://gitlab
 
 After the build has passed, your new website is available at `https://<YourUsername>.gitlab.io/<your-hugo-site>/`.
 
+{{% note %}}
+Make sure your `baseURL` key-value in your [site configuration](/getting-started/configuration/) reflects the full URL of your GitLab pages repository if you're using the default GitLab Pages URL (e.g., `https://<YourUsername>.gitlab.io/<your-hugo-site>/`) and not a custom domain.
+{{% /note %}}
+
 ## Next Steps
 
 GitLab supports using custom CNAME's and TLS certificates. For more details on GitLab Pages, see the [GitLab Pages setup documentation](https://about.gitlab.com/2016/04/07/gitlab-pages-setup/).

docs/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/).