diff --git a/site/_docs/configuration.md b/site/_docs/configuration.md index d09c5ab7..ac05a989 100644 --- a/site/_docs/configuration.md +++ b/site/_docs/configuration.md @@ -448,9 +448,9 @@ The `projects/foo_project.md` would have the `layout` set to `foobar` instead of ## Default Configuration -Jekyll runs with the following configuration options by default. Unless -alternative settings for these options are explicitly specified in the -configuration file or on the command-line, Jekyll will run using these options. +Jekyll runs with the following configuration options by default. Alternative +settings for these options can be explicitly specified in the configuration +file or on the command-line.
There are two unsupported kramdown options
diff --git a/site/_docs/continuous-integration.md b/site/_docs/continuous-integration.md index 5e8a700b..17823e1b 100644 --- a/site/_docs/continuous-integration.md +++ b/site/_docs/continuous-integration.md @@ -60,7 +60,7 @@ HTML::Proofer.new("./_site").run {% endhighlight %} Options are given as a second argument to `.new`, and are encoded in a -symbol-keyed Ruby Hash. More information about the configuration options, +symbol-keyed Ruby Hash. For more information about the configuration options, check out `html-proofer`'s README file. [2]: https://github.com/gjtorikian/html-proofer @@ -69,7 +69,7 @@ check out `html-proofer`'s README file. This file is used to configure your Travis builds. Because Jekyll is built with Ruby and requires RubyGems to install, we use the Ruby language build -environment. Below is a sample `.travis.yml` file, and what follows that is +environment. Below is a sample `.travis.yml` file, followed by an explanation of each line. {% highlight yaml %} diff --git a/site/_docs/deployment-methods.md b/site/_docs/deployment-methods.md index ddf571d4..04dda9f2 100644 --- a/site/_docs/deployment-methods.md +++ b/site/_docs/deployment-methods.md @@ -107,9 +107,10 @@ If you want to maintain Jekyll inside your existing Rails app, [Jekyll-Admin](ht ## Amazon S3 -If you want to host your site in Amazon S3, you can do so with -[s3_website](https://github.com/laurilehmijoki/s3_website) application. It will -push your site to Amazon S3 where it can be served like any web server, +If you want to host your site in Amazon S3, you can do so by +using the [s3_website](https://github.com/laurilehmijoki/s3_website) +application. It will push your site to Amazon S3 where it can be served like +any web server, dynamically scaling to almost unlimited traffic. This approach has the benefit of being about the cheapest hosting option available for low-volume blogs as you only pay for what you use.