diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml
index 78df2218dd..e549c1ec2b 100644
--- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml
+++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml
@@ -77,7 +77,7 @@ processes, the identifier for the language must be constructed as in
 BCP 47 comprises two Internet Engineering Task Force documents,
 referred to separately as RFC 5646 and RFC 4647; over time, other IETF
 documents may succeed these as the best current practice.</note>. This
-<emph rend="bold">same</emph> identifier has to be used to identify
+<emph>same</emph> identifier has to be used to identify
 the corresponding <gi>language</gi> element in the TEI header, if one
 is present.</p>
 <p>The first part of BCP 47 is called <ref target="#CH-BIBL-4"><title>Tags for Identifying
@@ -227,9 +227,9 @@ dates, and predefined value lists.</note></p></div>
     storey</soCalled> version (as in <ref target="#fig1">figure
     1</ref> in the examples from Umpush, or URW Bookman L Demi Bold).
     We say that the single and double-storey symbols both represent
-    one and the same the same <emph rend="bold">abstract
+    one and the same the same <emph>abstract
     character</emph> <mentioned>a</mentioned> using two different
-    <emph rend="bold">glyphs</emph>. Similarly, an uppercase
+    <emph>glyphs</emph>. Similarly, an uppercase
     <mentioned>A</mentioned> in a serif typeface has additional
     strokes that are absent from the same letter when printed using a
     sans-serif typeface, so that once again we have differing glyphs