Websites
/
lektor-website
mirror of https://github.com/lektor/lektor-website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #51 from johnwheeler/master 

minor doc proofing
This commit is contained in:
Armin Ronacher 2016-01-11 18:34:05 +01:00
parent fbfe6b4809 4fa93e15f4
commit bee8c4e80d
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/docs/content/flow/contents.lr
View File

@ -15,7 +15,7 @@ This allows you to build complex pages made from individual components.
When you add a `flow` field to one of your models you essentially gain the
ability to attach as many blocks as you want into this field. Each block
corresponds to a specific [Flow Block Models :ref](../../models/flow/) and
corresponds to a specific [Flow Block Model :ref](../../models/flow/) and
can render a separate template.
This is a very powerful feature as it allows you to be very flexible in the

6
content/docs/project/file/contents.lr
View File

@ -19,14 +19,14 @@ extension or Lektor will not be able to find it. When Lektor looks for a
project it looks upwards from the current folder until it finds a single
file with the `.lektorproject` extension and that's then the root of the project.
!! It's possible to build a Lektor project in the absence of a Project file
but this usage his heavily discouraged. It exists primarily for quick
!! It's possible to build a Lektor project in the absence of a Project file,
but this usage is heavily discouraged. It exists primarily for quick
testing situations. But don't be confused if you encounter a Lektor project
that does not come with a corresponding project file.
## Config Sections
Within the project file there are various configuration selections. The
Within the project file there are various configuration sections. The
following sections currently exist:
### `[project]`