dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix a few punctuation errors

This commit is contained in:
Jesse Pinho 2014-12-24 16:14:08 -06:00
parent f3a274377a
commit 52085d2e34
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/_docs/pages.md
View File

@ -60,7 +60,7 @@ and associated URLs might look like:
### Named folders containing index HTML files ### Named folders containing index HTML files
There is nothing wrong with the above method, however some people like to keep There is nothing wrong with the above method. However, some people like to keep
their URLs free from things like filename extensions. To achieve clean URLs for their URLs free from things like filename extensions. To achieve clean URLs for
pages using Jekyll, you simply need to create a folder for each top-level page pages using Jekyll, you simply need to create a folder for each top-level page
you want, and then place an `index.html` file in each page’s folder. This way you want, and then place an `index.html` file in each page’s folder. This way

8
site/_docs/plugins.md
View File

@ -13,8 +13,8 @@ having to modify the Jekyll source itself.
<div class="note info"> <div class="note info">
<h5>Plugins on GitHub Pages</h5> <h5>Plugins on GitHub Pages</h5>
<p> <p>
<a href="http://pages.github.com/">GitHub Pages</a> is powered by Jekyll, <a href="http://pages.github.com/">GitHub Pages</a> is powered by Jekyll.
however all Pages sites are generated using the <code>--safe</code> option However, all Pages sites are generated using the <code>--safe</code> option
to disable custom plugins for security reasons. Unfortunately, this means to disable custom plugins for security reasons. Unfortunately, this means
your plugins won’t work if you’re deploying to GitHub Pages.<br><br> your plugins won’t work if you’re deploying to GitHub Pages.<br><br>
You can still use GitHub Pages to publish your site, but you’ll need to You can still use GitHub Pages to publish your site, but you’ll need to
@ -68,8 +68,8 @@ A generator is a subclass of `Jekyll::Generator` that defines a `generate`
method, which receives an instance of method, which receives an instance of
[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb). [`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb).
Generation is triggered for its side-effects, the return value of `generate` is Because generation is triggered for its side effects, the return value of `generate` is
ignored. Jekyll does not assume any particular side-effect to happen, it just ignored. Jekyll does not assume any particular side effect to happen---it just
runs the method. runs the method.
Generators run after Jekyll has made an inventory of the existing content, and Generators run after Jekyll has made an inventory of the existing content, and

2
site/_docs/templates.md
View File

@ -303,7 +303,7 @@ You can also choose to include file fragments relative to the current file:
You won't need to place your included content within the `_includes` directory. Instead, You won't need to place your included content within the `_includes` directory. Instead,
the inclusion is specifically relative to the file where the tag is being used. For example, the inclusion is specifically relative to the file where the tag is being used. For example,
if `_posts/2014-09-03-my-file.markdown` uses the `include_relative` tag, the included file if `_posts/2014-09-03-my-file.markdown` uses the `include_relative` tag, the included file
must be within the `_posts` directory, or one of it's subdirectories. You cannot include must be within the `_posts` directory, or one of its subdirectories. You cannot include
files in other locations. files in other locations.
All the other capabilities of the `include` tag are available to the `include_relative` tag, All the other capabilities of the `include` tag are available to the `include_relative` tag,