Typo in the doc

graniteds · Dec 10, 2014 · b397264 · b397264
1 parent 0e493b6
commit b397264
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/reference-docs/src/asciidoc/graniteds-datamanagement-flex.adoc b/reference-docs/src/asciidoc/graniteds-datamanagement-flex.adoc
@@ -1538,11 +1538,11 @@ org.granite.tide.hibernate4.Hibernate4ChangeSetIntegrator
 ----
 
 Once this is configured, it's also necessary to configure the client to be able to merge these incoming +ChangeSet+ objects
-correctly. This can be done easily by setting up a +ChangeSetMerger+ components in your client context.
+correctly. This can be done easily by setting up a +ChangeMerger+ components in your client context.
 
 [source,java]
 ----
-Tide.getInstance().addComponents([ChangeSetMerger]);
+Tide.getInstance().addComponents([ChangeMerger]);
 ----
 
 When all this is set up, *all* server to client updates will be sent as +ChangeSet+ objects.
diff --git a/reference-docs/src/asciidoc/graniteds-datamanagement-javafx.adoc b/reference-docs/src/asciidoc/graniteds-datamanagement-javafx.adoc
@@ -1117,11 +1117,11 @@ org.granite.tide.hibernate4.Hibernate4ChangeSetIntegrator
 ----
 
 Once this is configured, it's also necessary to configure the client to be able to merge these incoming +ChangeSet+ objects
-correctly. This can be done easily by setting up the +ChangeSetMerger+ components, for example:
+correctly. This can be done easily by setting up the +ChangeMerger+ components, for example:
 
 [source,java]
 ----
-context.set(new ChangeSetMerger());
+context.set(new ChangeMerger());
 ----
 
 When all this is set up, *all* server to client updates will be sent as +ChangeSet+ objects.