Mercurial > piecrust2
changeset 818:e24360c2946a
docs: Fix line-end / new-line issues
author | Raoul Bourquin <raoul@ccczh.ch> |
---|---|
date | Mon, 14 Nov 2016 02:55:02 +0100 |
parents | 4cbd534f68b0 |
children | 31f2964d034a |
files | docs/docs/03_content/01_creating-pages.md docs/docs/03_content/03_formatters.md docs/docs/03_content/08_iterators.md |
diffstat | 3 files changed, 6 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/docs/03_content/01_creating-pages.md Mon Nov 14 02:53:39 2016 +0100 +++ b/docs/docs/03_content/01_creating-pages.md Mon Nov 14 02:55:02 2016 +0100 @@ -4,8 +4,8 @@ In PieCrust, creating pages is a matter of creating a text file in the correct place with the correct name. This mostly depends on the [page sources][src] -you're using, but we can go over how it works for the sources involved in the -[default content model][dcm]. +you're using, but we can go over how it works for the sources involved in +the [default content model][dcm]. We will also mention the `chef prepare` command, which semi-automates the process of creating pages by letting you type a lot less than what would be
--- a/docs/docs/03_content/03_formatters.md Mon Nov 14 02:53:39 2016 +0100 +++ b/docs/docs/03_content/03_formatters.md Mon Nov 14 02:55:02 2016 +0100 @@ -6,8 +6,8 @@ contents that you write go through a _formatter_ before the page is rendered or baked. PieCrust ships with 2 standard formatters: [Markdown][] and [Textile][]. -The formatter used on a page is determined by the `format` setting in the page's -[configuration header][pageconf]: +The formatter used on a page is determined by the `format` setting in the +page's [configuration header][pageconf]: * `markdown` for Markdown * `textile` for Textile
--- a/docs/docs/03_content/08_iterators.md Mon Nov 14 02:53:39 2016 +0100 +++ b/docs/docs/03_content/08_iterators.md Mon Nov 14 02:55:02 2016 +0100 @@ -4,8 +4,8 @@ --- PieCrust returns _iterator objects_ as template data in several cases: -`pagination.posts`, `assets`, `site.pages`, etc. Any time there's a list of -_stuff_, you can bet it's returned as an _iterator object_. +`pagination.posts`, `assets`, `site.pages`, etc. Any time there's a list +of _stuff_, you can bet it's returned as an _iterator object_. At first glance, there's not much difference with a simple list: