From 511c58d4e18479d930023ead214a83b1af0f0bec Mon Sep 17 00:00:00 2001 From: Roberto Bonvallet Date: Thu, 7 Jun 2012 12:03:45 -0400 Subject: [PATCH 1/3] s/reqeust/request/ --- docs/development.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development.rst b/docs/development.rst index 90bdb43..4174a1e 100644 --- a/docs/development.rst +++ b/docs/development.rst @@ -71,7 +71,7 @@ Feature / Hotfix / Release branches follow a `Successful Git Branching Model`_ . Each release is tagged. -When submitting patches, please place your feature/change in its own branch prior to opening a pull reqeust on GitHub_. +When submitting patches, please place your feature/change in its own branch prior to opening a pull request on GitHub_. .. _Git: http://git-scm.org From d5fada7e1d56b11a3b451c61c08a5931f99d9d0a Mon Sep 17 00:00:00 2001 From: Roberto Bonvallet Date: Thu, 7 Jun 2012 12:04:22 -0400 Subject: [PATCH 2/3] s/ebpub/epub/ --- docs/development.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/development.rst b/docs/development.rst index 4174a1e..2ea96cb 100644 --- a/docs/development.rst +++ b/docs/development.rst @@ -210,7 +210,7 @@ Then, to build an HTML version of the docs, simply run the following from the ** Your ``docs/_build/html`` directory will then contain an HTML representation of the documentation, ready for publication on most web servers. -You can also generate the documentation in **ebpub**, **latex**, **json**, *&c* similarly. +You can also generate the documentation in **epub**, **latex**, **json**, *&c* similarly. .. admonition:: GitHub Pages From 05ea3c35fce21410cbd697b290cda65dc117fbbe Mon Sep 17 00:00:00 2001 From: Roberto Bonvallet Date: Thu, 7 Jun 2012 12:05:22 -0400 Subject: [PATCH 3/3] s/Jeckyl/Jekyll/ --- docs/development.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development.rst b/docs/development.rst index 2ea96cb..03b6929 100644 --- a/docs/development.rst +++ b/docs/development.rst @@ -216,7 +216,7 @@ You can also generate the documentation in **epub**, **latex**, **json**, *&c* s To push the documentation up to `GitHub Pages`_, you will first need to run `sphinx-to-github`_ against your ``docs/_build/html`` directory. - GitHub Pages are powered by an HTML generation system called Jeckyl_, which is configured to ignore files and folders that begin with "``_``" (*ie.* **_static**). + GitHub Pages are powered by an HTML generation system called Jekyll_, which is configured to ignore files and folders that begin with "``_``" (*ie.* **_static**). @@ -238,7 +238,7 @@ You can also generate the documentation in **epub**, **latex**, **json**, *&c* s .. _`reStructured Text`: http://docutils.sourceforge.net/rst.html .. _Sphinx: http://sphinx.pocoo.org .. _`GitHub Pages`: http://pages.github.com -.. _Jeckyl: http://github.com/mojombo/jekyll +.. _Jekyll: http://github.com/mojombo/jekyll .. _`sphinx-to-github`: http://github.com/michaeljones/sphinx-to-github ----------