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

Typos and line wrapping

This commit is contained in:
chrisfinazzo 2015-10-19 12:06:46 -04:00
parent d63acc140d
commit 36a41cd224
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
site/_docs/configuration.md
View File

@ -653,8 +653,8 @@ class Jekyll::Converters::Markdown::MyCustomProcessor
end end
{% endhighlight %} {% endhighlight %}
Once you've created your class and have it properly setup either as a plugin in Once you've created your class and have it properly set up either as a plugin
the `_plugins` folder or as a gem, specify it in your `_config.yml`: in the `_plugins` folder or as a gem, specify it in your `_config.yml`:
{% highlight yaml %} {% highlight yaml %}
markdown: MyCustomProcessor markdown: MyCustomProcessor

2
site/_docs/contributing.md
View File

@ -43,7 +43,7 @@ Test Dependencies
----------------- -----------------
To run the test suite and build the gem you'll need to install Jekyll's To run the test suite and build the gem you'll need to install Jekyll's
dependencies. Simply run this command to get all setup: dependencies. Simply run this command to get all set up:
$ script/bootstrap $ script/bootstrap

2
site/_docs/deployment-methods.md
View File

@ -112,7 +112,7 @@ That's why rrsync wrapper shall be installed. If it is not already installed by
- Put it to the bin subdirectory of your home folder (```~/bin```) - Put it to the bin subdirectory of your home folder (```~/bin```)
- Make it executable (```chmod +x```) - Make it executable (```chmod +x```)
#### Step 2: Setup certificate-based ssh access (server side) #### Step 2: Set up certificate-based ssh access (server side)
[This process is described in a lot of places in the net](https://wiki.gentoo.org/wiki/SSH#Passwordless_Authentication). We will not cover it here. What is different from usual approach is to put the restriction to certificate-based authorization in ```~/.ssh/authorized_keys```). We will launch ```rrsync``` utility and supply it with the folder it shall have read-write access to: [This process is described in a lot of places in the net](https://wiki.gentoo.org/wiki/SSH#Passwordless_Authentication). We will not cover it here. What is different from usual approach is to put the restriction to certificate-based authorization in ```~/.ssh/authorized_keys```). We will launch ```rrsync``` utility and supply it with the folder it shall have read-write access to: