From f4392efff68e42c61db9acdc0f845ea92f033372 Mon Sep 17 00:00:00 2001
From: Keith Donald <kdonald@vmware.com>
Date: Fri, 16 Oct 2009 23:14:01 +0000
Subject: [PATCH] polish

git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@2140 50f2f4bb-b051-0410-bef5-90022cba6387
---
 spring-framework-reference/src/validation.xml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/spring-framework-reference/src/validation.xml b/spring-framework-reference/src/validation.xml
index 7931f43a5fb..3aabf04d706 100644
--- a/spring-framework-reference/src/validation.xml
+++ b/spring-framework-reference/src/validation.xml
@@ -1599,10 +1599,14 @@ public void testDefaultSpelMappingBehavior() {
 				<title>Registering Explicit Mappings</title>
 				<para>
 					When default mapping rules are not sufficient, explicit mapping rules can be registered by obtaining a <classname>MapperBuilder</classname> and using it to construct a <classname>Mapper</classname>.
-					Explicit mapping rules always override the default.
+					Explicit mapping rules always override the default:
 				</para>
 				<programlisting language="java"><![CDATA[
-MappingBuilder<PersonDto, Person> builder = MappingFactory.mappingBuilder(PersonDto.class, Person.class)]]>
+MappperBuilder<PersonDto, Person> builder = MappingFactory.mappingBuilder(PersonDto.class, Person.class)
+builder.addMapping(...);
+builder.addMapping(...);
+Mapper<PersonDto, Person> mapper = builder.getMapper();
+]]>
 				</programlisting>			
 				<section id="mapping.SpelMapper-Explicit-differentFieldNames">
 					<title>Mapping between two fields with different names</title>