Merge pull request #1066 from xiemaisi/fix-qhelp-backticks

jbj · web-flow · commit a90e4a7bdf3f · 2019-03-08T19:06:48.000+01:00
Fix qhelp backticks
diff --git a/cpp/ql/src/Likely Bugs/Conversion/LossyFunctionResultCast.qhelp b/cpp/ql/src/Likely Bugs/Conversion/LossyFunctionResultCast.qhelp
@@ -8,7 +8,7 @@
 
 </overview>
 <recommendation>
-<p>Consider changing the surrounding expression to match the floating point type. If rounding is intended, explicitly round using a standard function such as `trunc`, `floor` or `round`.</p>
+<p>Consider changing the surrounding expression to match the floating point type. If rounding is intended, explicitly round using a standard function such as <code>trunc</code>, <code>floor</code> or <code>round</code>.</p>
 
 </recommendation>
 <example><sample src="LossyFunctionResultCast.cpp" />
diff --git a/cpp/ql/src/Likely Bugs/Likely Typos/FutileParams.qhelp b/cpp/ql/src/Likely Bugs/Likely Typos/FutileParams.qhelp
@@ -8,9 +8,9 @@
 <p>A function is called with arguments despite having an empty parameter list. This may indicate
 that the incorrect function is being called, or that the author misunderstood the function.</p>
 
-<p>In C, a function declared with an empty parameter list `()` is considered to have an unknown
+<p>In C, a function declared with an empty parameter list <code>()</code> is considered to have an unknown
 parameter list, and therefore can be called with any set of arguments. To declare a function
-which takes no arguments, you must use `(void)` as the parameter list in any forward declarations.
+which takes no arguments, you must use <code>(void)</code> as the parameter list in any forward declarations.
 In C++, either style of declaration indicates that the function accepts no arguments.</p>
 
 </overview>
diff --git a/javascript/ql/src/Security/CWE-116/DoubleEscaping.qhelp b/javascript/ql/src/Security/CWE-116/DoubleEscaping.qhelp
@@ -35,7 +35,7 @@ or garbled output.
 <p>
 Use a (well-tested) sanitization library if at all possible. These libraries are much more
 likely to handle corner cases correctly than a custom implementation. For URI encoding,
-you can use the standard `encodeURIComponent` and `decodeURIComponent` functions.
+you can use the standard <code>encodeURIComponent</code> and <code>decodeURIComponent</code> functions.
 </p>
 <p>
 Otherwise, make sure to always escape the escape character first, and unescape it last.
