diff --git a/docs/_docs/configuration/markdown.md b/docs/_docs/configuration/markdown.md index 865d6e7e..30471526 100644 --- a/docs/_docs/configuration/markdown.md +++ b/docs/_docs/configuration/markdown.md @@ -51,7 +51,7 @@ currently supported options:

-For more details about these options have a look at the [Kramdown configuration documentation](https://kramdown.gettalong.org/options.html). +For more details about these options have a look at the [Kramdown configuration documentation](https://kramdown.gettalong.org/options.html). ### Redcarpet diff --git a/docs/_docs/continuous-integration/circleci.md b/docs/_docs/continuous-integration/circleci.md index 9380a90c..c8b77c05 100644 --- a/docs/_docs/continuous-integration/circleci.md +++ b/docs/_docs/continuous-integration/circleci.md @@ -38,7 +38,7 @@ CircleCI detects when `Gemfile` is present is will automatically run `bundle ins ## 3. Testing -The most basic test that can be run is simply seeing if `jekyll build` actually works. This is a blocker, a dependency if you will, for other tests you might run on the generate site. So we'll run Jekyll, via Bundler, in the `dependencies` phase. +The most basic test that can be run is simply seeing if `jekyll build` actually works. This is a blocker, a dependency if you will, for other tests you might run on the generate site. So we'll run Jekyll, via Bundler, in the `dependencies` phase. ```yaml dependencies: diff --git a/docs/_docs/deployment/automated.md b/docs/_docs/deployment/automated.md index 8ba9cc53..d3efa610 100644 --- a/docs/_docs/deployment/automated.md +++ b/docs/_docs/deployment/automated.md @@ -11,7 +11,7 @@ CI. These services run a script when there's a commit on your Git repository. You might want this script to build the site, run tests over the output then deploy it to the -service of your choice. +service of your choice. We have guides for the following providers: diff --git a/docs/_docs/liquid.md b/docs/_docs/liquid.md index a7c21550..7151cb19 100644 --- a/docs/_docs/liquid.md +++ b/docs/_docs/liquid.md @@ -5,7 +5,7 @@ redirect_from: "/docs/templates/" --- Jekyll uses the [Liquid](https://shopify.github.io/liquid/) templating language -to process templates. +to process templates. Generally in Liquid you output content using two curly braces e.g. {% raw %}`{{ variable }}`{% endraw %} and perform logic statements by diff --git a/docs/_docs/step-by-step/05-includes.md b/docs/_docs/step-by-step/05-includes.md index 9aab5f6e..7eb3a986 100644 --- a/docs/_docs/step-by-step/05-includes.md +++ b/docs/_docs/step-by-step/05-includes.md @@ -17,7 +17,7 @@ in an `_includes` folder. Includes are useful for having a single source for source code that repeats around the site or for improving the readability. Navigation source code can get complex so sometimes it's nice to move it into an -include. +include. ## Include usage diff --git a/docs/_docs/upgrading/2-to-3.md b/docs/_docs/upgrading/2-to-3.md index 7bfbce5c..5f4ef8fb 100644 --- a/docs/_docs/upgrading/2-to-3.md +++ b/docs/_docs/upgrading/2-to-3.md @@ -115,7 +115,7 @@ relative_permalinks: true ### Permalinks no longer automatically add a trailing slash -In Jekyll 2, any URL constructed from the `permalink:` field had a trailing slash (`/`) added to it automatically. Jekyll 3 no longer adds a trailing slash automatically to `permalink:` URLs. This can potentially result in old links to pages returning a 404 error. For example, suppose a page previously contained the YAML `permalink: /:year-:month-:day-:title` that resulted in the URL `example.com/2016-02-01-test/` (notice the trailing slash), Jekyll internally generates a folder named `2016-02-01-test`. In Jekyll 3, the same `permalink:` generate the file `2016-02-01-test.html` and the URL for the same page will be `example.com/2016-02-01-test`, and consequently any links to the old URL will result in a 404 error. In order to maintain the same URLs and avoid this problem, a trailing slash should be added to the `permalink:` field, for example `permalink: /:year-:month-:day-:title/`. +In Jekyll 2, any URL constructed from the `permalink:` field had a trailing slash (`/`) added to it automatically. Jekyll 3 no longer adds a trailing slash automatically to `permalink:` URLs. This can potentially result in old links to pages returning a 404 error. For example, suppose a page previously contained the YAML `permalink: /:year-:month-:day-:title` that resulted in the URL `example.com/2016-02-01-test/` (notice the trailing slash), Jekyll internally generates a folder named `2016-02-01-test`. In Jekyll 3, the same `permalink:` generate the file `2016-02-01-test.html` and the URL for the same page will be `example.com/2016-02-01-test`, and consequently any links to the old URL will result in a 404 error. In order to maintain the same URLs and avoid this problem, a trailing slash should be added to the `permalink:` field, for example `permalink: /:year-:month-:day-:title/`. ### All my posts are gone! Where'd they go! diff --git a/docs/_tutorials/navigation.md b/docs/_tutorials/navigation.md index 69fbb908..ff66daf7 100644 --- a/docs/_tutorials/navigation.md +++ b/docs/_tutorials/navigation.md @@ -591,7 +591,7 @@ The `group_by` filter groups the collection content by `category`. More specific ```yaml [ {"name": "getting-started", "items": [Sample 1, Sample 2],"size": 2}, - {"name": "configuration", "items": [Topic 1, Topic 2], "size": 2}, + {"name": "configuration", "items": [Topic 1, Topic 2], "size": 2}, {"name": "deployment", "items": [Widget 1, Widget 2, "size": 2} ] ```