From e27dcd2616d86d317d711e1d36a8a7762ecda46e Mon Sep 17 00:00:00 2001 From: Parker Mauney <5124113+ParkerM@users.noreply.github.com> Date: Sun, 22 Jul 2018 17:50:10 -0500 Subject: [PATCH] Fix duplicate typos in reference docs --- src/docs/asciidoc/index.adoc | 3 +-- src/site/xdoc/index.xml | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/docs/asciidoc/index.adoc b/src/docs/asciidoc/index.adoc index a27063fb..8f763717 100644 --- a/src/docs/asciidoc/index.adoc +++ b/src/docs/asciidoc/index.adoc @@ -792,8 +792,7 @@ We previously saw that updating by using `modifyAttributes` is the recommended a the task of calculating attribute modifications and constructing `ModificationItem` arrays accordingly. `DirContextAdapter` can do all of this for us, as follows: -.Updating using using `DirContextAdapter` -==== +.Updating using `DirContextAdapter` [[modify-modifyAttributes]] [source,java] [subs="verbatim,quotes"] diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml index 9dbcc919..baac2cda 100644 --- a/src/site/xdoc/index.xml +++ b/src/site/xdoc/index.xml @@ -15,7 +15,7 @@ creating a DirContext, looping through NamingEnumerations, handling exceptions and cleaning up resources. This leaves the programmer to handle the important stuff - where to find data (DNs and Filters) and - what do do with it (map to and from domain objects, bind, modify, + what to do with it (map to and from domain objects, bind, modify, unbind, etc.), in the same way that JdbcTemplate relieves the programmer of all but the actual SQL and how the data maps to the domain model.