1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/declarative/codingconventions.qdoc b/doc/src/declarative/codingconventions.qdoc
index 8222ebce41..f65e53c678 100644
--- a/doc/src/declarative/codingconventions.qdoc
+++ b/doc/src/declarative/codingconventions.qdoc
@@ -53,7 +53,7 @@ Through our documentation and examples, QML objects are always structured in the
 For better readability, we separate these different parts with an empty line.
 
 
-For example, a hypothetical \e photo QML object would look like this:
+For example, a hypothetical \i photo QML object would look like this:
 
 \snippet doc/src/snippets/declarative/codingconventions/photo.qml 0
 
@@ -61,7 +61,7 @@ For example, a hypothetical \e photo QML object would look like this:
 \section1 Grouped Properties
 
 If using multiple properties from a group of properties,
-we use the \e {group notation} rather than the \e {dot notation} to improve readability.
+we use the \i {group notation} rather than the \i {dot notation} to improve readability.
 
 For example, this:
 
@@ -77,7 +77,7 @@ can be written like this:
 QML and JavaScript do not enforce private properties like C++. There is a need
 to hide these private properties, for example, when the properties are part of
 the implementation. As a convention, private properties begin with two
-\e underscore characters. For example, \c __area, is a property that is
+\i underscore characters. For example, \c __area, is a property that is
 accessible but is not meant for public use. Note that QML and JavaScript will
 grant the user access to these properties.