diff --git a/modules/ROOT/pages/programming-languages/C.adoc b/modules/ROOT/pages/programming-languages/C.adoc
index 6dcd443..6663285 100644
--- a/modules/ROOT/pages/programming-languages/C.adoc
+++ b/modules/ROOT/pages/programming-languages/C.adoc
@@ -770,7 +770,7 @@ are not implemented as inline functions or preprocessor macros.
 The compiler lacks knowledge of such wrappers outside the
 translation unit which defines them, which means that some
 optimizations and security checks are not performed. Adding
-`__attribute__` annotations to function
+`+__attribute__+` annotations to function
 declarations can remedy this to some extent, but these
 annotations have to be maintained carefully for feature parity
 with the standard implementation.
@@ -788,7 +788,7 @@ propagate its return value, your wrapper should be declared
 with `warn_unused_result` as well.
 
 * Duplicating the buffer length checks based on the
-`__builtin_object_size` GCC builtin is
+`+__builtin_object_size+` GCC builtin is
 desirable if the wrapper processes arrays. (This
 functionality is used by the
 `-D_FORTIFY_SOURCE=2` checks to guard
diff --git a/modules/ROOT/pages/programming-languages/Java.adoc b/modules/ROOT/pages/programming-languages/Java.adoc
index bf5aa98..eb7f785 100644
--- a/modules/ROOT/pages/programming-languages/Java.adoc
+++ b/modules/ROOT/pages/programming-languages/Java.adoc
@@ -375,7 +375,7 @@ necessarily constant during the lifetime of your JNI module.
 Storing it in a global variable is therefore incorrect.
 Particularly if you are dealing with callbacks, you may have to
 store the pointer in a thread-local variable (defined with
-`__thread`). It is, however, best to avoid the
+`+__thread+`). It is, however, best to avoid the
 complexity of calling back into Java code.
 
 Keep in mind that C/C++ and Java are different languages,
diff --git a/modules/ROOT/pages/tasks/Tasks-Processes.adoc b/modules/ROOT/pages/tasks/Tasks-Processes.adoc
index 14e924c..3d549b8 100644
--- a/modules/ROOT/pages/tasks/Tasks-Processes.adoc
+++ b/modules/ROOT/pages/tasks/Tasks-Processes.adoc
@@ -266,8 +266,8 @@ variables.
 The Autoconf macro `AC_GNU_SOURCE` ensures this.
 
 * Check for the presence of the `secure_getenv`
-and `__secure_getenv` function. The Autoconf
-directive `AC_CHECK_FUNCS([__secure_getenv secure_getenv])`
+and `+__secure_getenv+` function. The Autoconf
+directive `+AC_CHECK_FUNCS([__secure_getenv secure_getenv])+`
 performs these checks.
 
 * Arrange for a proper definition of the
@@ -286,7 +286,7 @@ restrictions or cause a privileged process to behave in an
 unexpected way.
 
 Either the `secure_getenv` function or the
-`__secure_getenv` is available from GNU libc.
+`+__secure_getenv+` is available from GNU libc.
 
 [[ex-Defensive_Coding-Tasks-secure_getenv]]
 .Obtaining a definition for `secure_getenv`