diff --git a/spring-framework-reference/src/mvc.xml b/spring-framework-reference/src/mvc.xml
index 97e028e2c8879a20b30f2a9816d9e7dd13806a2b..7fa9d929e3542b19a4d7ac35e85d85ac31f98324 100644
--- a/spring-framework-reference/src/mvc.xml
+++ b/spring-framework-reference/src/mvc.xml
@@ -16,7 +16,7 @@
     wide range of flexible handling methods. With the introduction of Spring
     3.0, the <interfacename>@Controller</interfacename> mechanism also allows
     you to create RESTful Web sites and applications, through the
-    <interfacename>@PathVarariable</interfacename> annotation and other
+    <interfacename>@PathVariable</interfacename> annotation and other
     features.</para>
 
     <sidebar id="mvc-open-for-extension">
diff --git a/spring-framework-reference/src/testing.xml b/spring-framework-reference/src/testing.xml
index 3300600a016b2959710efce32ea47b25b55f3f41..778abf9d8f610bf3d87a8bc8e6ea9abfac6b214f 100644
--- a/spring-framework-reference/src/testing.xml
+++ b/spring-framework-reference/src/testing.xml
@@ -1652,17 +1652,17 @@ code, etc? Or what? If my rewording is wrong, revise to clarify. What does using
           <para>The <emphasis>Spring TestContext Framework</emphasis> offers
           full integration with JUnit 4.5+ through a custom runner (tested on
           JUnit 4.5, 4.6, and 4.7). By annotating test classes with
-          <literal>@Runwith(SpringJUnit4ClassRunner.class)</literal>,
+          <literal>@RunWith(SpringJUnit4ClassRunner.class)</literal>,
           developers can implement standard JUnit 4.5+ unit and integration
           tests and simultaneously reap the benefits of the TestContext
           framework such as support for loading application contexts,
           dependency injection of test instances, transactional test method
-          execution, and so on. The following code listing displays the
-          minimal requirements for configuring a test class to run with the
-          custom Spring Runner. @TestExecutionListeners is configured with an
-          empty list in order to disable the default listeners, which
-          otherwise would require an ApplicationContext to be configured
-          through @ContextConfiguration.</para>
+          execution, and so on. The following code listing displays the minimal
+          requirements for configuring a test class to run with the custom Spring
+          Runner. <interfacename>@TestExecutionListeners</interfacename> is
+          configured with an empty list in order to disable the default listeners,
+          which otherwise would require an ApplicationContext to be configured
+          through <interfacename>@ContextConfiguration</interfacename>.</para>
 
           <programlisting language="java">@RunWith(SpringJUnit4ClassRunner.class)
 @TestExecutionListeners({})