Mentioned UTF-8 as encoding

content/docs/content/contents.lr

@@ -64,9 +64,9 @@ can be overridden in the content file with the `_template` field.
 ## Content File Format
 
 So now it's time to talk about the content file.  The content file is just a
-text file with the `.lr` extension.  It can be edited with any text editor
-that supports UTF-8 as character encoding.  This file consists of multiple
-data fields according to the model.  The format is very simple:
+UTF-8 encoded text file with the `.lr` extension.  It can be edited with any
+text editor that supports UTF-8 as character encoding.  This file consists of
+multiple data fields according to the model.  The format is very simple:
 
 ```
 _model: page

content/docs/models/contents.lr

@@ -14,9 +14,9 @@ easier later to generate beautiful looking HTML.
 
 Models are the blueprints for your pages.  They define which fields exist and
 what goes into them.  Models are stored in the `models` folder in your project
-and are basic INI files.  Models can have any name but if no model has been
-explicitly selected, the model with the name `page` will be used.  So having
-a model with that name is always a good idea.
+and are basic UTF-8 encoded INI files.  Models can have any name but if no
+model has been explicitly selected, the model with the name `page` will be
+used.  So having a model with that name is always a good idea.
 
 Here is an example of a very basic model (`models/page.ini`):
 

content/docs/project/file/contents.lr

@@ -6,7 +6,8 @@ body:
 
 The project file holds the main configuration of the project and is used to
 identify the project for the user interface.  The project file is an INI file
-and the minimal content is the name of the project:
+(UTF-8 encoded like everything else in Lektor) and the minimal content is the
+name of the project:
 
 ```ini
 [project]