From cac58738c9fe730ce37224d970d21eda5cb16473 Mon Sep 17 00:00:00 2001
From: Stephane Nicoll <snicoll@pivotal.io>
Date: Fri, 1 Jul 2016 10:58:15 +0200
Subject: [PATCH] Polish

Closes gh-1089
---
 src/asciidoc/core-beans.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/asciidoc/core-beans.adoc b/src/asciidoc/core-beans.adoc
index e834ada05dc..0a419ff3445 100644
--- a/src/asciidoc/core-beans.adoc
+++ b/src/asciidoc/core-beans.adoc
@@ -2680,12 +2680,12 @@ understand the "why" as well as the "how" behind it.
 ----
 
 To create such a proxy, you insert a child `<aop:scoped-proxy/>` element into a scoped
-bean definition. (See <<beans-factory-scopes-other-injection-proxies>> and
-<<xsd-configuration>>.) Why do definitions of beans scoped at the `request`, `session`,
-`globalSession` and custom-scope levels require the `<aop:scoped-proxy/>` element ?
+bean definition (see <<beans-factory-scopes-other-injection-proxies>> and
+<<xsd-configuration>>). Why do definitions of beans scoped at the `request`, `session`,
+`globalSession` and custom-scope levels require the `<aop:scoped-proxy/>` element?
 Let's examine the following singleton bean definition and contrast it with what you need
-to define for the aforementioned scopes. (The following `userPreferences` bean
-definition as it stands is __incomplete.)__
+to define for the aforementioned scopes (note that the following `userPreferences` bean
+definition as it stands is __incomplete__).
 
 [source,xml,indent=0]
 [subs="verbatim,quotes"]