Add backticks in "Checked Iterators" topic

Author: Rageking8

docs/standard-library/checked-iterators.md

@@ -12,18 +12,18 @@ Checked iterators ensure that the bounds of your container are not overwritten.
 
 ## Remarks
 
-For information about how to disable warnings that are generated by checked iterators, see [_SCL_SECURE_NO_WARNINGS](../standard-library/scl-secure-no-warnings.md).
+For information about how to disable warnings that are generated by checked iterators, see [`_SCL_SECURE_NO_WARNINGS`](../standard-library/scl-secure-no-warnings.md).
 
-You can use the [\_ITERATOR\_DEBUG\_LEVEL](../standard-library/iterator-debug-level.md) preprocessor macro to enable or disable the checked iterators feature. If _ITERATOR_DEBUG_LEVEL is defined as 1 or 2, unsafe use of iterators causes a runtime error and the program is terminated. If defined as 0, checked iterators are disabled. By default, the value for _ITERATOR_DEBUG_LEVEL is 0 for release builds and 2 for debug builds.
+You can use the [`_ITERATOR_DEBUG_LEVEL`](../standard-library/iterator-debug-level.md) preprocessor macro to enable or disable the checked iterators feature. If `_ITERATOR_DEBUG_LEVEL` is defined as 1 or 2, unsafe use of iterators causes a runtime error and the program is terminated. If defined as 0, checked iterators are disabled. By default, the value for `_ITERATOR_DEBUG_LEVEL` is 0 for release builds and 2 for debug builds.
 
 > [!IMPORTANT]
-> Older documentation and source code may refer to the [_SECURE_SCL](../standard-library/secure-scl.md) macro. Use _ITERATOR_DEBUG_LEVEL to control _SECURE_SCL. For more information, see [_ITERATOR_DEBUG_LEVEL](../standard-library/iterator-debug-level.md).
+> Older documentation and source code may refer to the [`_SECURE_SCL`](../standard-library/secure-scl.md) macro. Use `_ITERATOR_DEBUG_LEVEL` to control `_SECURE_SCL`. For more information, see [`_ITERATOR_DEBUG_LEVEL`](../standard-library/iterator-debug-level.md).
 
-When _ITERATOR_DEBUG_LEVEL is defined as 1 or 2, these iterator checks are performed:
+When `_ITERATOR_DEBUG_LEVEL` is defined as 1 or 2, these iterator checks are performed:
 
-- All standard iterators (for example, [vector::iterator](../standard-library/vector-class.md#iterator)) are checked.
+- All standard iterators (for example, [`vector::iterator`](../standard-library/vector-class.md#iterator)) are checked.
 
-- If an output iterator is a checked iterator, calls to standard library functions such as [std::copy](../standard-library/algorithm-functions.md#copy) get checked behavior.
+- If an output iterator is a checked iterator, calls to standard library functions such as [`std::copy`](../standard-library/algorithm-functions.md#copy) get checked behavior.
 
 - If an output iterator is an unchecked iterator, calls to standard library functions cause compiler warnings.
 
@@ -50,7 +50,7 @@ When _ITERATOR_DEBUG_LEVEL is defined as 1 or 2, these iterator checks are perfo
    :::column-end:::
 :::row-end:::
 
-When _ITERATOR_DEBUG_LEVEL is defined as 0:
+When `_ITERATOR_DEBUG_LEVEL` is defined as 0:
 
 - All standard iterators are unchecked. Iterators can move beyond the container boundaries, which leads to undefined behavior.
 
@@ -60,11 +60,11 @@ When _ITERATOR_DEBUG_LEVEL is defined as 0:
 
 A checked iterator refers to an iterator that calls `invalid_parameter_handler` if you attempt to move past the boundaries of the container. For more information about `invalid_parameter_handler`, see [Parameter Validation](../c-runtime-library/parameter-validation.md).
 
-The iterator adaptors that support checked iterators are [checked_array_iterator Class](../standard-library/checked-array-iterator-class.md) and [unchecked_array_iterator Class](../standard-library/unchecked-array-iterator-class.md).
+The iterator adaptors that support checked iterators are [`checked_array_iterator` Class](../standard-library/checked-array-iterator-class.md) and [`unchecked_array_iterator` Class](../standard-library/unchecked-array-iterator-class.md).
 
 ## Examples
 
-When you compile by using _ITERATOR_DEBUG_LEVEL set to 1 or 2, a runtime error will occur if you attempt to access an element that is outside the bounds of the container by using the indexing operator of certain classes.
+When you compile by using `_ITERATOR_DEBUG_LEVEL` set to 1 or 2, a runtime error will occur if you attempt to access an element that is outside the bounds of the container by using the indexing operator of certain classes.
 
 ```cpp
 // checked_iterators_1.cpp
@@ -91,7 +91,7 @@ int main()
 
 This program prints "67" then pops up an assertion failure dialog box with additional information about the failure.
 
-Similarly, when you compile by using _ITERATOR_DEBUG_LEVEL set to 1 or 2, a runtime error will occur if you attempt to access an element by using `front` or `back` in container classes when the container is empty.
+Similarly, when you compile by using `_ITERATOR_DEBUG_LEVEL` set to 1 or 2, a runtime error will occur if you attempt to access an element by using `front` or `back` in container classes when the container is empty.
 
 ```cpp
 // checked_iterators_2.cpp
@@ -113,7 +113,7 @@ int main()
 
 This program pops up an assertion failure dialog box with additional information about the failure.
 
-The following code demonstrates various iterator use-case scenarios with comments about each. By default, _ITERATOR_DEBUG_LEVEL is set to 2 in Debug builds, and to 0 in Retail builds.
+The following code demonstrates various iterator use-case scenarios with comments about each. By default, `_ITERATOR_DEBUG_LEVEL` is set to 2 in Debug builds, and to 0 in Retail builds.
 
 ```cpp
 // checked_iterators_3.cpp