Fix a few minor issues in the docs (#6494)

Merge pull request 6494

docs/_docs/continuous-integration/buddyworks.md

@@ -29,7 +29,7 @@ Whenever you make a push to the selected branch, the Jekyll action runs `jekyll
 
 If you prefer configuration as code over GUI, you can generate a `buddy.yml` that will create a pipeline with the Jekyll action once you push it to the target branch:
 
-```ruby
+```yaml
 - pipeline: "Build and Deploy Jekyll site"
   trigger_mode: "ON_EVERY_PUSH"
   ref_name: "master"

docs/_docs/continuous-integration/circleci.md

@@ -25,7 +25,7 @@ The easiest way to manage dependencies for a Jekyll project (with or without Cir
 
 [4]: http://bundler.io/gemfile.html
 
-```yaml
+```ruby
 source 'https://rubygems.org'
 
 ruby '2.4.0'

docs/_docs/deployment-methods.md

@@ -20,7 +20,7 @@ Read this [Jekyll step-by-step guide](https://www.netlify.com/blog/2015/10/28/a-
 
 [Aerobatic](https://www.aerobatic.com) has custom domains, global CDN distribution, basic auth, CORS proxying, and a growing list of plugins all included.
 
-Automating the deployment of a Jekyll site is simple. See our [Jekyll docs](https://www.aerobatic.com/docs/static-site-generators/#jekyll) for more details. Your built `_site` folder is deployed to our highly-available, globally distributed hosting service.
+Automating the deployment of a Jekyll site is simple. See their [Jekyll docs](https://www.aerobatic.com/docs/static-site-generators/#jekyll) for more details. Your built `_site` folder is deployed to their highly-available, globally distributed hosting service.
 
 ## Kickster