diff --git a/docs/pages/pmd/rules/pom/errorprone.md b/docs/pages/pmd/rules/pom/errorprone.md
index 3315e4f3b7..d32917742d 100644
--- a/docs/pages/pmd/rules/pom/errorprone.md
+++ b/docs/pages/pmd/rules/pom/errorprone.md
@@ -53,7 +53,7 @@ The following types are considered valid: pom, jar, maven-plugin, ejb, war, ear,
 **Priority:** Medium (3)
 
 Using that expression in dependency declarations seems like a shortcut, but it can go wrong.
-By far the most common problem is the use of 6.1.0-SNAPSHOT in a BOM or parent POM.
+By far the most common problem is the use of ${project.version} in a BOM or parent POM.
 
 ```
 //dependency/version/text[contains(@Image,'{project.version}')]
diff --git a/pmd-xml/src/main/resources/category/pom/errorprone.xml b/pmd-xml/src/main/resources/category/pom/errorprone.xml
index c05f70b96b..1d238a882b 100644
--- a/pmd-xml/src/main/resources/category/pom/errorprone.xml
+++ b/pmd-xml/src/main/resources/category/pom/errorprone.xml
@@ -62,7 +62,7 @@ The following types are considered valid: pom, jar, maven-plugin, ejb, war, ear,
           externalInfoUrl="${pmd.website.baseurl}/pmd_rules_pom_errorprone.html#projectversionasdependencyversion">
         <description>
 Using that expression in dependency declarations seems like a shortcut, but it can go wrong.
-By far the most common problem is the use of ${project.version} in a BOM or parent POM.
+By far the most common problem is the use of &#x24;{project.version} in a BOM or parent POM.
         </description>
         <priority>3</priority>
         <properties>