diff --git a/content/contents.lr b/content/contents.lr
index d382d071..50ae0b5a 100644
--- a/content/contents.lr
+++ b/content/contents.lr
@@ -55,7 +55,7 @@ text:
* **Deploy Anywhere** Because Lektor
builds out 100% static HTML you can deploy them to any host (including S3,
- github pages, any web host, etc.).
+ GitHub Pages, any web host, etc.).
* **Cross Platform** It runs on
Linux, OSX and Windows.
* **100% File Based** All
diff --git a/content/docs/api/db/expression/ge/contents.lr b/content/docs/api/db/expression/ge/contents.lr
index 834400ea..2acb0052 100644
--- a/content/docs/api/db/expression/ge/contents.lr
+++ b/content/docs/api/db/expression/ge/contents.lr
@@ -6,7 +6,7 @@ type: operator
---
body:
-This evalutes to true if the left side compares larger than the right side
+This evaluates to true if the left side compares larger than the right side
or equal to it. This behavior works best with [integers
:ref](../../types/integer/) or [floats :ref](../../types/float/).
diff --git a/content/docs/api/db/expression/gt/contents.lr b/content/docs/api/db/expression/gt/contents.lr
index ff5f6d6d..3d96d714 100644
--- a/content/docs/api/db/expression/gt/contents.lr
+++ b/content/docs/api/db/expression/gt/contents.lr
@@ -6,7 +6,7 @@ type: operator
---
body:
-This evalutes to true if the left side compares larger than the right side.
+This evaluates to true if the left side compares larger than the right side.
This behavior works best with [integers :ref](../../types/integer/)
or [floats :ref](../../types/float/).
diff --git a/content/docs/api/db/expression/le/contents.lr b/content/docs/api/db/expression/le/contents.lr
index c52b76f9..6ec15b4d 100644
--- a/content/docs/api/db/expression/le/contents.lr
+++ b/content/docs/api/db/expression/le/contents.lr
@@ -6,7 +6,7 @@ type: operator
---
body:
-This evalutes to true if the left side compares smaller than the right side
+This evaluates to true if the left side compares smaller than the right side
or equal to it. This behavior works best with [integers
:ref](../../types/integer/) or [floats :ref](../../types/float/).
diff --git a/content/docs/api/db/expression/lt/contents.lr b/content/docs/api/db/expression/lt/contents.lr
index ebdd1543..5195694d 100644
--- a/content/docs/api/db/expression/lt/contents.lr
+++ b/content/docs/api/db/expression/lt/contents.lr
@@ -6,7 +6,7 @@ type: operator
---
body:
-This evalutes to true if the left side compares smaller than the right side
+This evaluates to true if the left side compares smaller than the right side
or equal to it. This behavior works best with [integers
:ref](../../types/integer/) or [floats :ref](../../types/float/).
diff --git a/content/docs/api/db/expression/ne/contents.lr b/content/docs/api/db/expression/ne/contents.lr
index 97b3abd2..d9caf2b1 100644
--- a/content/docs/api/db/expression/ne/contents.lr
+++ b/content/docs/api/db/expression/ne/contents.lr
@@ -7,7 +7,7 @@ type: operator
body:
This checks if the left side of the expression does not match the right side
-by doing a exact comparision:
+by doing an exact comparison:
## Example
diff --git a/content/docs/api/db/obj/is-discoverable/contents.lr b/content/docs/api/db/obj/is-discoverable/contents.lr
index 9847e4c4..50979d7c 100644
--- a/content/docs/api/db/obj/is-discoverable/contents.lr
+++ b/content/docs/api/db/obj/is-discoverable/contents.lr
@@ -14,7 +14,7 @@ check if a record is considered non-discoverable by Lektor or not. In
particular a hidden record is also considered undiscoverable.
Undiscoverable records can be queried and final pages will be built but they
-are excempt from queries of the record. This is useful for pages that should
+are exempt from queries of the record. This is useful for pages that should
be built but not show up yet on overview pages. For instance this can be used
to implement drafts of blog posts or similar things.
diff --git a/content/docs/api/db/query/order-by/contents.lr b/content/docs/api/db/query/order-by/contents.lr
index c93c1dfb..b4952e9e 100644
--- a/content/docs/api/db/query/order-by/contents.lr
+++ b/content/docs/api/db/query/order-by/contents.lr
@@ -9,7 +9,7 @@ signature: *fields
body:
This is a handy way to change the order of the items returned. The default
-order is defined in the model config but can be overriden this way. The
+order is defined in the model config but can be overridden this way. The
method accepts an arbitrary number of strings, each of which refers to the
name of a field. If a string is prefixed with a minus sign (`-`) then the
order is reversed.
diff --git a/content/docs/api/db/type/contents.lr b/content/docs/api/db/type/contents.lr
index 0b1a9e90..6dfbb9cf 100644
--- a/content/docs/api/db/type/contents.lr
+++ b/content/docs/api/db/type/contents.lr
@@ -15,7 +15,7 @@ body:
The fields in [Records :ref](../record/) use types to specify the behavior of
the values. Lektor comes with a wide range of [built-in field types
:ref](../types/) but it is possible to build your own by subclassing types
-class. A type is instanciated with two parameters: a reference to the
+class. A type is instantiated with two parameters: a reference to the
[Environment :ref](../../environment/) that it belongs to and a dictionary
with configuration options from the ini file.
diff --git a/content/docs/api/environment/load-config/contents.lr b/content/docs/api/environment/load-config/contents.lr
index 3cd5e10e..e9c7cc1e 100644
--- a/content/docs/api/environment/load-config/contents.lr
+++ b/content/docs/api/environment/load-config/contents.lr
@@ -7,7 +7,7 @@ summary: Loads the current config from the project file.
body:
Because the environment is reused between builds, the config is not cached
-on the environment but needs to be expicitly loaded. This happens with
+on the environment but needs to be explicitly loaded. This happens with
the help of the `load_config` method. It returns a config object that
gives access to the settings in the project file.
diff --git a/content/docs/api/plugins/events/process-template-context/contents.lr b/content/docs/api/plugins/events/process-template-context/contents.lr
index db5c189d..9518769d 100644
--- a/content/docs/api/plugins/events/process-template-context/contents.lr
+++ b/content/docs/api/plugins/events/process-template-context/contents.lr
@@ -23,7 +23,7 @@ unless they are explicitly passed to it.
The filename of the template is passed as `template` but is only available
if the template was indeed loaded from the templates folder. There are many
-more places where templates are rendered in in those cases the value will
+more places where templates are rendered in those cases the value will
not be provided.
## Example
diff --git a/content/docs/api/project/from-file/contents.lr b/content/docs/api/project/from-file/contents.lr
index ac48a616..9dd04152 100644
--- a/content/docs/api/project/from-file/contents.lr
+++ b/content/docs/api/project/from-file/contents.lr
@@ -8,7 +8,7 @@ summary: Loads a project from a project file.
---
body:
-This is the most common way to create a project insteance. It's a class
+This is the most common way to create a project instance. It's a class
method that given the path to a project file will load the project. If
the file does not exist then `None` is returned.
diff --git a/content/docs/api/publisher/output-path/contents.lr b/content/docs/api/publisher/output-path/contents.lr
index 9b54871c..468a7d14 100644
--- a/content/docs/api/publisher/output-path/contents.lr
+++ b/content/docs/api/publisher/output-path/contents.lr
@@ -10,6 +10,6 @@ body:
This attribute holds the path to the folder where the build process put the
final artifacts. Usually a publisher walks that folder and does something
-with all contents of it. The publishers however are heavily encourated to
+with all contents of it. The publishers however are heavily encouraged to
ignore the special `.lektor` folder which contains lektor specific information
that should not end up on the resulting server.
diff --git a/content/docs/api/templates/filters/latlongformat/contents.lr b/content/docs/api/templates/filters/latlongformat/contents.lr
index 36d11ab8..2c69fa9e 100644
--- a/content/docs/api/templates/filters/latlongformat/contents.lr
+++ b/content/docs/api/templates/filters/latlongformat/contents.lr
@@ -9,7 +9,7 @@ summary: Formats the latitude and longitude into a string
body:
This formats a latitude and longitude tuple into a human readable string
-in the format format degrees, minutes and seconds. See also [latformat
+in the format degrees, minutes and seconds. See also [latformat
:ref](../latformat/) and [longformat :ref](../longformat/).
## Examples
diff --git a/content/docs/api/utils/url-to/contents.lr b/content/docs/api/utils/url-to/contents.lr
index 192b217f..0c93cb18 100644
--- a/content/docs/api/utils/url-to/contents.lr
+++ b/content/docs/api/utils/url-to/contents.lr
@@ -1,6 +1,6 @@
title: url_to
---
-summary: Calculates the URL to a specific page realtive to the current.
+summary: Calculates the URL to a specific page relative to the current.
---
type: function
---
diff --git a/content/docs/cli/plugins/reinstall/contents.lr b/content/docs/cli/plugins/reinstall/contents.lr
index 7ea16038..37a44863 100644
--- a/content/docs/cli/plugins/reinstall/contents.lr
+++ b/content/docs/cli/plugins/reinstall/contents.lr
@@ -2,7 +2,7 @@ comment: This file is auto generated by dump-cli-help.py
---
title: reinstall
---
-summary: Reginstall all plugins.
+summary: Reinstall all plugins.
---
type: cmdlet
---
diff --git a/content/docs/content/alts/contents.lr b/content/docs/content/alts/contents.lr
index ad5bdff0..27d7b018 100644
--- a/content/docs/content/alts/contents.lr
+++ b/content/docs/content/alts/contents.lr
@@ -78,5 +78,5 @@ targeted, different files will be used. This table visualizes this:
Alternatives have a special behavior with regards to paths. They alternative
code does not exist in the path! This can be confusing at first, but has the
advantage that they automatically work in most places as the paths are the
-same for differnent alternatives. For more information see
+same for different alternatives. For more information see
[Alternatives and Paths :ref](../paths/#alternatives-and-paths).
diff --git a/content/docs/content/urls/contents.lr b/content/docs/content/urls/contents.lr
index 2493d09a..2c6040dd 100644
--- a/content/docs/content/urls/contents.lr
+++ b/content/docs/content/urls/contents.lr
@@ -96,7 +96,7 @@ Lektor by default will prefer relative URLs. This makes it possible to easily
host a website below a certain folder without having to do anything special to
make this work. However there are some features which will require the use of
an absolute or fully canonical (external) URL. For instance sitemaps or Atom
-feeds do not work with realtive URLs. In this case the absolute URL path has
+feeds do not work with relative URLs. In this case the absolute URL path has
to be configured.
You can pick the default for URL generation in the project configuration.
diff --git a/content/docs/deployment/ftp/contents.lr b/content/docs/deployment/ftp/contents.lr
index a0c70484..36ee7f07 100644
--- a/content/docs/deployment/ftp/contents.lr
+++ b/content/docs/deployment/ftp/contents.lr
@@ -10,7 +10,7 @@ body:
FTP is a very old but well supported protocol. Lektor can publish through it
but to speed up the operation it has to make certain concessions. In
particular it needs to maintain a “listing file” to remember the state of
-the files as FTP does not support any form of file comparisions. This means
+the files as FTP does not support any form of file comparisons. This means
that you cannot use Lektor in addition to another system to publish files
to your FTP server. It's an either/or thing.
@@ -33,7 +33,7 @@ target = sftp://myuser:mypassword@ftp.example.com/var/www/example
FTP is considered a largely insecure protocol for Lektor. As such if you
want to use it you should keep your project file save as credentials will
-be most likely embedded there. Alternatively you can set the credentails
+be most likely embedded there. Alternatively you can set the credentials
via the command line with the `--username` and `--password` option (or via the
environment variables `LEKTOR_DEPLOY_USERNAME` and `LEKTOR_DEPLOY_PASSWORD`)
though this will mean that most likely deploys via the admin interface
diff --git a/content/docs/deployment/ghpages/contents.lr b/content/docs/deployment/ghpages/contents.lr
index 66415602..ef82ceb4 100644
--- a/content/docs/deployment/ghpages/contents.lr
+++ b/content/docs/deployment/ghpages/contents.lr
@@ -1,6 +1,6 @@
title: GitHub Pages
---
-summary: Deploys to github pages.
+summary: Deploys to GitHub Pages.
---
body:
@@ -60,7 +60,7 @@ the feature in the GitHub help center:
## 404 Pages
-Per convenention the file named `404.html` is used as placeholder if a page
+Per convention the file named `404.html` is used as placeholder if a page
cannot be found. You can create such a page by creating a `404.html/contents.lr`
file.
diff --git a/content/docs/deployment/rsync/contents.lr b/content/docs/deployment/rsync/contents.lr
index 852f9ff9..c47997a0 100644
--- a/content/docs/deployment/rsync/contents.lr
+++ b/content/docs/deployment/rsync/contents.lr
@@ -7,7 +7,7 @@ body:
`rsync://username@server/path/to/folder`
This deploys via SSH and rsync to a remote server. This is the recommended
-way to deploy if the system supports it as it is a very fast and realiable
+way to deploy if the system supports it as it is a very fast and reliable
way. It uses the system's SSH config so for authentication just configure
SSH as you would normally do. The `username` part is optional and defaults
to the current user that is signed into the machine or whatever is picked up
diff --git a/content/docs/models/children/contents.lr b/content/docs/models/children/contents.lr
index 7006101e..d33a70ab 100644
--- a/content/docs/models/children/contents.lr
+++ b/content/docs/models/children/contents.lr
@@ -76,7 +76,7 @@ keys are available:
* `enabled`: if set to `yes` pagination becomes enabled. It's off by
default.
-* `per_page`: this controls how many children are are shown per page. If
+* `per_page`: this controls how many children are shown per page. If
pagination is enabled and this is not set, an implicit default of `20`
is assumed.
diff --git a/content/docs/plugins/contents.lr b/content/docs/plugins/contents.lr
index bea34a7e..cac8bba0 100644
--- a/content/docs/plugins/contents.lr
+++ b/content/docs/plugins/contents.lr
@@ -23,7 +23,7 @@ Plugins can be added to a Lektor project in two different ways:
## Installing Plugins
-For completely automated plugin managment just open your project file in a
+For completely automated plugin management just open your project file in a
text editor and edit or extend the `[packages]` section. Just add a line
for each plugin in the form `name = version`:
diff --git a/templates/blog-layout.html b/templates/blog-layout.html
index 6ff8ccbf..26faf6f1 100644
--- a/templates/blog-layout.html
+++ b/templates/blog-layout.html
@@ -16,7 +16,7 @@
About This Blog
“The Transcript” is the blog about Lektor, a new solution in static content managment.
+ }}">Lektor, a new solution in static content management.
Subscribe for the latest news about Lektor as well as content
management and web development.
diff --git a/templates/layout.html b/templates/layout.html
index cc50dbcd..9e41e11d 100644
--- a/templates/layout.html
+++ b/templates/layout.html
@@ -50,7 +50,7 @@