Temporarily escape monospaced text that will not be linked

Escape elements that we know cannot be converted to a javadoc link.

See gh-43239

Author: philwebb

spring-boot-project/spring-boot-actuator-autoconfigure/src/docs/antora/modules/api/pages/rest/actuator/logfile.adoc

@@ -23,7 +23,7 @@ include::partial$rest/actuator/logfile/entire/http-response.adoc[]
 
 NOTE: Retrieving part of the log file is not supported when using Jersey.
 
-To retrieve part of the log file, make a `GET` request to `/actuator/logfile` by using the `Range` header, as shown in the following curl-based example:
+To retrieve part of the log file, make a `GET` request to `/actuator/logfile` by using the `+Range+` header, as shown in the following curl-based example:
 
 include::partial$rest/actuator/logfile/range/curl-request.adoc[]
 

spring-boot-project/spring-boot-docs/src/docs/antora/modules/appendix/pages/test-auto-configuration/index.adoc

@@ -2,4 +2,4 @@
 [[appendix.test-auto-configuration]]
 = Test Auto-configuration Annotations
 
-This appendix describes the `@...Test` auto-configuration annotations that Spring Boot provides to test slices of your application.
+This appendix describes the `+@...Test+` auto-configuration annotations that Spring Boot provides to test slices of your application.

spring-boot-project/spring-boot-docs/src/docs/antora/modules/appendix/pages/test-auto-configuration/slices.adoc

@@ -1,6 +1,6 @@
 [[appendix.test-auto-configuration.slices]]
 = Test Slices
 
-The following table lists the various `@...Test` annotations that can be used to test slices of your application and the auto-configuration that they import by default:
+The following table lists the various `+@...Test+` annotations that can be used to test slices of your application and the auto-configuration that they import by default:
 
 include::partial$slices/documented-slices.adoc[]

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/aot.adoc

@@ -43,7 +43,7 @@ For Maven, this works by setting the `profiles` configuration of the `spring-boo
 </profile>
 ----
 
-For Gradle, you need to configure the `ProcessAot` task:
+For Gradle, you need to configure the `+ProcessAot+` task:
 
 [source,gradle]
 ----

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/application.adoc

@@ -17,7 +17,7 @@ You can extend from that so that your implementation gets a chance to handle the
 If, for whatever reason, you cannot handle the exception, return `null` to give another implementation a chance to handle the exception.
 
 `FailureAnalyzer` implementations must be registered in `META-INF/spring.factories`.
-The following example registers `ProjectConstraintViolationFailureAnalyzer`:
+The following example registers `+ProjectConstraintViolationFailureAnalyzer+`:
 
 [source,properties]
 ----

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/data-access.adoc

@@ -28,7 +28,7 @@ app:
     pool-size: 30
 ----
 
-Assuming that `SomeDataSource` has regular JavaBean properties for the URL, the username, and the pool size, these settings are bound automatically before the `DataSource` is made available to other components.
+Assuming that `+SomeDataSource+` has regular JavaBean properties for the URL, the username, and the pool size, these settings are bound automatically before the `DataSource` is made available to other components.
 
 Spring Boot also provides a utility builder class, called `DataSourceBuilder`, that can be used to create one of the standard data sources (if it is on the classpath).
 The builder can detect which one to use based on what is available on the classpath.
@@ -244,7 +244,7 @@ Alternatively, if `ImplicitNamingStrategy` or `PhysicalNamingStrategy` beans are
 By default, Spring Boot configures the physical naming strategy with `CamelCaseToUnderscoresNamingStrategy`.
 Using this strategy, all dots are replaced by underscores and camel casing is replaced by underscores as well.
 Additionally, by default, all table names are generated in lower case.
-For example, a `TelephoneNumber` entity is mapped to the `telephone_number` table.
+For example, a `+TelephoneNumber+` entity is mapped to the `telephone_number` table.
 If your schema requires mixed-case identifiers, define a custom `CamelCaseToUnderscoresNamingStrategy` bean, as shown in the following example:
 
 include-code::spring/MyHibernateConfiguration[]
@@ -288,7 +288,7 @@ For details, see {url-hibernate-userguide}#caching-provider-jcache[the Hibernate
 [[howto.data-access.dependency-injection-in-hibernate-components]]
 == Use Dependency Injection in Hibernate Components
 
-By default, Spring Boot registers a `BeanContainer` implementation that uses the `BeanFactory` so that converters and entity listeners can use regular dependency injection.
+By default, Spring Boot registers a `org.hibernate.resource.beans.container.spi.BeanContainer` implementation that uses the `BeanFactory` so that converters and entity listeners can use regular dependency injection.
 
 You can disable or tune this behavior by registering a `HibernatePropertiesCustomizer` that removes or changes the `hibernate.resource.beans.container` property.
 
@@ -317,8 +317,8 @@ Building upon xref:how-to:data-access.adoc#howto.data-access.configure-two-datas
 include-code::MyAdditionalEntityManagerFactoryConfiguration[]
 
 The example above creates an `EntityManagerFactory` using the `DataSource` bean qualified with `@Qualifier("second")`.
-It scans entities located in the same package as `Order`.
-It is possible to map additional JPA properties using the `app.jpa` namespace.
+It scans entities located in the same package as `+Order+`.
+It is possible to map additional JPA properties using the `+app.jpa+` namespace.
 The use of `@Bean(defaultCandidate=false)` allows the `secondJpaProperties` and `secondEntityManagerFactory` beans to be defined without interfering with auto-configured beans of the same type.
 
 NOTE: The {url-spring-framework-docs}/core/beans/dependencies/factory-autowire.html#beans-factory-autowire-candidate[Spring Framework reference documentation] describes this feature in more details.

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/deployment/installing.adoc

@@ -33,9 +33,9 @@ SuccessExitStatus=143
 WantedBy=multi-user.target
 ----
 
-IMPORTANT: Remember to change the `Description`, `User`, `Group`, `ExecStart` and `WorkingDirectory` fields for your application.
+IMPORTANT: Remember to change the `+Description+`, `+User+`, `+Group+`, `+ExecStart+` and `+WorkingDirectory+` fields for your application.
 
-NOTE: The `ExecStart` field does not declare the script action command, which means that the `run` command is used by default.
+NOTE: The `+ExecStart+` field does not declare the script action command, which means that the `run` command is used by default.
 
 The user that runs the application, the PID file, and the console log file are managed by `systemd` itself and therefore must be configured by using appropriate fields in the '`service`' script.
 Consult the https://www.freedesktop.org/software/systemd/man/systemd.service.html[service unit configuration man page] for more details.
@@ -206,7 +206,7 @@ The following property substitutions are supported with the default script:
 | `auto`
 
 | `initInfoProvides`
-| The `Provides` section of "`INIT INFO`"
+| The `+Provides+` section of "`INIT INFO`"
 | `${task.baseName}`
 | `${project.artifactId}`
 
@@ -236,7 +236,7 @@ The following property substitutions are supported with the default script:
 | `${project.name}`
 
 | `initInfoDescription`
-| `Description` section of "`INIT INFO`".
+| `+Description+` section of "`INIT INFO`".
 | `${project.description}` (falling back to `${task.baseName}`)
 | `${project.description}` (falling back to `${project.name}`)
 

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/deployment/traditional-deployment.adoc

@@ -75,7 +75,7 @@ This means that, in addition to being deployable to a servlet container, you can
 To convert an existing non-web Spring application to a Spring Boot application, replace the code that creates your `ApplicationContext` and replace it with calls to `SpringApplication` or `SpringApplicationBuilder`.
 Spring MVC web applications are generally amenable to first creating a deployable war application and then migrating it later to an executable war or jar.
 
-To create a deployable war by extending `SpringBootServletInitializer` (for example, in a class called `Application`) and adding the Spring Boot `@SpringBootApplication` annotation, use code similar to that shown in the following example:
+To create a deployable war by extending `SpringBootServletInitializer` (for example, in a class called `+Application+`) and adding the Spring Boot `@SpringBootApplication` annotation, use code similar to that shown in the following example:
 
 include-code::MyApplication[tag=!main]
 
@@ -87,14 +87,14 @@ Static resources can be moved to `/public` (or `/static` or `/resources` or `/ME
 The same applies to `messages.properties` (which Spring Boot automatically detects in the root of the classpath).
 
 Vanilla usage of Spring `DispatcherServlet` and Spring Security should require no further changes.
-If you have other features in your application (for instance, using other servlets or filters), you may need to add some configuration to your `Application` context, by replacing those elements from the `web.xml`, as follows:
+If you have other features in your application (for instance, using other servlets or filters), you may need to add some configuration to your `+Application+` context, by replacing those elements from the `web.xml`, as follows:
 
 * A `@Bean` of type `Servlet` or `ServletRegistrationBean` installs that bean in the container as if it were a `<servlet/>` and `<servlet-mapping/>` in `web.xml`.
 * A `@Bean` of type `Filter` or `FilterRegistrationBean` behaves similarly (as a `<filter/>` and `<filter-mapping/>`).
 * An `ApplicationContext` in an XML file can be added through an `@ImportResource` in your `Application`.
   Alternatively, cases where annotation configuration is heavily used already can be recreated in a few lines as `@Bean` definitions.
 
-Once the war file is working, you can make it executable by adding a `main` method to your `Application`, as shown in the following example:
+Once the war file is working, you can make it executable by adding a `main` method to your `+Application+`, as shown in the following example:
 
 include-code::MyApplication[tag=main]
 

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/docker-compose.adoc

@@ -9,7 +9,7 @@ This section includes topics relating to the Docker Compose support in Spring Bo
 == Customizing the JDBC URL
 
 When using `JdbcConnectionDetails` with Docker Compose, the parameters of the JDBC URL
-can be customized by applying the `org.springframework.boot.jdbc.parameters` label to the
+can be customized by applying the `+org.springframework.boot.jdbc.parameters+` label to the
 service. For example:
 
 [source,yaml]

spring-boot-project/spring-boot-docs/src/docs/antora/modules/how-to/pages/logging.adoc

@@ -170,7 +170,7 @@ dependencies {
 
 NOTE: The Log4j starters gather together the dependencies for common logging requirements (such as having Tomcat use `java.util.logging` but configuring the output using Log4j 2).
 
-NOTE: To ensure that debug logging performed using `java.util.logging` is routed into Log4j 2, configure its https://logging.apache.org/log4j/2.x/log4j-jul.html[JDK logging adapter] by setting the `java.util.logging.manager` system property to `org.apache.logging.log4j.jul.LogManager`.
+NOTE: To ensure that debug logging performed using `java.util.logging` is routed into Log4j 2, configure its https://logging.apache.org/log4j/2.x/log4j-jul.html[JDK logging adapter] by setting the `java.util.logging.manager` system property to `+org.apache.logging.log4j.jul.LogManager+`.