Fix a few punctuation errors
This commit is contained in:
		
							parent
							
								
									f3a274377a
								
							
						
					
					
						commit
						52085d2e34
					
				|  | @ -60,7 +60,7 @@ and associated URLs might look like: | |||
| 
 | ||||
| ### 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 | ||||
| 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 | ||||
|  |  | |||
|  | @ -13,8 +13,8 @@ having to modify the Jekyll source itself. | |||
| <div class="note info"> | ||||
|   <h5>Plugins on GitHub Pages</h5> | ||||
|   <p> | ||||
|     <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 | ||||
|     <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 | ||||
|     to disable custom plugins for security reasons. Unfortunately, this means | ||||
|     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 | ||||
|  | @ -68,8 +68,8 @@ A generator is a subclass of `Jekyll::Generator` that defines a `generate` | |||
| method, which receives an instance of | ||||
| [`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb). | ||||
| 
 | ||||
| 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 | ||||
| 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 | ||||
| runs the method. | ||||
| 
 | ||||
| Generators run after Jekyll has made an inventory of the existing content, and | ||||
|  |  | |||
|  | @ -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, | ||||
| 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 | ||||
| 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. | ||||
| 
 | ||||
| All the other capabilities of the `include` tag are available to the `include_relative` tag, | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue