Merge pull request #1566 from drumonii:double-backtick-with-apostrophes

* pr/1566:
  Missing some double backticks with apostrophes

src/docs/asciidoc/core/core-aop-api.adoc

@@ -736,7 +736,7 @@ options that are preferable if you don't need such control.
 The `ProxyFactoryBean`, like other Spring `FactoryBean` implementations, introduces a
 level of indirection. If you define a `ProxyFactoryBean` with name `foo`, what objects
 referencing `foo` see is not the `ProxyFactoryBean` instance itself, but an object
-created by the `ProxyFactoryBean`'s implementation of the `getObject()` method. This
+created by the ``ProxyFactoryBean``'s implementation of the `getObject()` method. This
 method will create an AOP proxy wrapping a target object.
 
 One of the most important benefits of using a `ProxyFactoryBean` or another IoC-aware

src/docs/asciidoc/integration.adoc

@@ -263,7 +263,7 @@ In the newly created application context called `remoting-servlet.xml`, we'll cr
 Now we're ready to link in the service at the client. No explicit handler mapping is
 specified, mapping request URLs onto services, so `BeanNameUrlHandlerMapping` will be
 used: Hence, the service will be exported at the URL indicated through its bean name
-within the containing `DispatcherServlet`'s mapping (as defined above):
+within the containing ``DispatcherServlet``'s mapping (as defined above):
 `'http://HOST:8080/remoting/AccountService'`.
 
 Alternatively, create a `HessianServiceExporter` in your root application context (e.g.
@@ -408,7 +408,7 @@ dispatcher's application context:
 	</bean>
 ----
 
-Such an exporter definition will be exposed through the `DispatcherServlet`'s standard
+Such an exporter definition will be exposed through the ``DispatcherServlet``'s standard
 mapping facilities, as explained in the section on Hessian.
 
 Alternatively, create an `HttpInvokerServiceExporter` in your root application context
@@ -1644,7 +1644,7 @@ synchronous receive calls is set using the property `setReceiveTimeout`.
 
 Some JMS providers allow the setting of default QOS values administratively through the
 configuration of the `ConnectionFactory`. This has the effect that a call to
-`MessageProducer`'s send method `send(Destination destination, Message message)` will
+``MessageProducer``'s send method `send(Destination destination, Message message)` will
 use different QOS default values than those specified in the JMS specification. In order
 to provide consistent management of QOS values, the `JmsTemplate` must therefore be
 specifically enabled to use its own QOS values by setting the boolean property
@@ -2427,7 +2427,7 @@ Spring also provides a generic JCA message endpoint manager which is not tied to
 for using any message listener type (e.g. a CCI MessageListener) and any
 provider-specific ActivationSpec object. Check out your JCA provider's documentation to
 find out about the actual capabilities of your connector, and consult
-`GenericMessageEndpointManager`'s javadoc for the Spring-specific configuration details.
+``GenericMessageEndpointManager``'s javadoc for the Spring-specific configuration details.
 
 [NOTE]
 ====
@@ -3163,7 +3163,7 @@ a container that does not provide an `MBeanServer`. To address this you can crea
 `MBeanServer` instance declaratively by adding an instance of the
 `org.springframework.jmx.support.MBeanServerFactoryBean` class to your configuration.
 You can also ensure that a specific `MBeanServer` is used by setting the value of the
-`MBeanExporter`'s `server` property to the `MBeanServer` value returned by an
+``MBeanExporter``'s `server` property to the `MBeanServer` value returned by an
 `MBeanServerFactoryBean`; for example:
 
 [source,xml,indent=0]

src/docs/asciidoc/web/webmvc-view.adoc

@@ -1538,7 +1538,7 @@ for more configuration examples.
 == XML Marshalling
 The `MarshallingView` uses an XML `Marshaller` defined in the `org.springframework.oxm`
 package to render the response content as XML. The object to be marshalled can be set
-explicitly using `MarhsallingView`'s `modelKey` bean property. Alternatively, the view
+explicitly using ``MarhsallingView``'s `modelKey` bean property. Alternatively, the view
 will iterate over all model properties and marshal the first type that is supported
 by the `Marshaller`. For more information on the functionality in the
 `org.springframework.oxm` package refer to the chapter <<oxm,Marshalling XML using O/X