The :option: syntax was generating Sphinx build warnings; switched to double backtick...

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@335843 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/ReleaseNotes.rst b/docs/ReleaseNotes.rst
index 15ae73e859e753198bac6e3b60102856c7e2dac8..c0ce10d6eb5376a104a83252008dede6abb0c516 100644 (file)
--- a/docs/ReleaseNotes.rst
+++ b/docs/ReleaseNotes.rst
@@ -103,8 +103,7 @@ Non-comprehensive list of changes in this release
 New Compiler Flags
 ------------------
 
-- :option:`-fstrict-float-cast-overflow` and
-  :option:`-fno-strict-float-cast-overflow`.
+- ``-fstrict-float-cast-overflow`` and ``-fno-strict-float-cast-overflow``.
 
   When a floating-point value is not representable in a destination integer
   type, the code has undefined behavior according to the language standard. By
@@ -112,7 +111,7 @@ New Compiler Flags
   'no-strict' option, Clang attempts to match the overflowing behavior of the
   target's native float-to-int conversion instructions.
 
-- :option: `-fforce-emit-vtables` and `-fno-force-emit-vtables`.
+- ``-fforce-emit-vtables`` and ``-fno-force-emit-vtables``.
 
    In order to improve devirtualization, forces emitting of vtables even in
    modules where it isn't necessary. It causes more inline virtual functions