[llvm] [NFC][CodingStandard] Fix text style for C++ keywords (PR #128932)

[Rahul Joshi via llvm-commits]

https://github.com/jurahul created https://github.com/llvm/llvm-project/pull/128932

Fix C++ keywords in Restrict Visibility section to use `` (inline literal) markup to be consistent with the rest of the doc.

>From b64573706c7f0364c5ed391f331f48eb6bff04e5 Mon Sep 17 00:00:00 2001
From: Rahul Joshi <rjoshi at nvidia.com>
Date: Wed, 26 Feb 2025 10:56:12 -0800
Subject: [PATCH] [NFC][CodingStandard] Fix text style for C++ keywords

- Fix C++ keywords in Restrict Visibility section to use `` (inline
  literal) markup to be consistent with the rest of the doc.
---
 llvm/docs/CodingStandards.rst | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/llvm/docs/CodingStandards.rst b/llvm/docs/CodingStandards.rst
index dde859d1e0f71..ad772f69127ad 100644
--- a/llvm/docs/CodingStandards.rst
+++ b/llvm/docs/CodingStandards.rst
@@ -1583,19 +1583,20 @@ Restrict Visibility
 ^^^^^^^^^^^^^^^^^^^
 
 Functions and variables should have the most restricted visibility possible.
-For class members, that means using appropriate `private`, `protected`, or `public`
-keyword to restrict their access. For non-member functions, variables, and classes,
-that means restricting visibility to a single `.cpp` file if it's not referenced
-outside that file.
+For class members, that means using appropriate ``private``, ``protected``, or
+``public`` keyword to restrict their access. For non-member functions, variables,
+and classes, that means restricting visibility to a single ``.cpp`` file if it's
+not referenced outside that file.
 
 Visibility of file-scope non-member variables and functions can be restricted to
-the current translation unit by using either the `static` keyword or an anonymous namespace.
-Anonymous namespaces are a great language feature that tells the C++ compiler that
-the contents of the namespace are only visible within the current translation unit,
-allowing more aggressive optimization and eliminating the possibility of symbol
-name collisions.  Anonymous namespaces are to C++ as `static` is to C functions and
-global variables.  While `static` is available in C++, anonymous namespaces are more
-general: they can make entire classes private to a file.
+the current translation unit by using either the ``static`` keyword or an anonymous
+namespace. Anonymous namespaces are a great language feature that tells the C++
+compiler that the contents of the namespace are only visible within the current
+translation unit, allowing more aggressive optimization and eliminating the
+possibility of symbol name collisions.  Anonymous namespaces are to C++ as
+``static`` is to C functions and global variables.  While ``static`` is available
+in C++, anonymous namespaces are more general: they can make entire classes
+private to a file.
 
 The problem with anonymous namespaces is that they naturally want to encourage
 indentation of their body, and they reduce locality of reference: if you see a