diff --git a/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html b/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html
index f36f840cd70..6e01dc4bb8b 100644
--- a/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html
+++ b/doc/org.eclipse.cdt.doc.isv/guide/dom/index.html
@@ -14,16 +14,29 @@ for CDT 3.0. Changes should be expected until further notified.
Model, is a programmatic way to see the underlying source code in both
a syntactic and semantic view using an Abstract Syntax Tree (AST) and
to allow changes in the AST to be reflected back out to the source
-code. Sounds simple enough, but with the complexity of the C and C++
-languages with an intermixing of pre-processor goodness, it certainly
-has it's challenges.
+code.
+
The syntactic view (which we sometimes call the physical view)
+represents the syntactic structure of the program. This is driven
+mainly by the grammar that the parser follows, mapping from terminals
+up to the entry rule in the grammer. This view fulfills the role of a
+traditional Abstract Syntax Tree, and you'll see that the classes that
+make up this view have AST in their name.
The semantic view (which we sometimes call the logical view)
+represent semantic elements in the program. These elements are
+generally types, variables, and functions. The JDT calls these things
+bindings, so we do to. However, the more general rule is that anything
+that links sub-branches of the AST is a binding.
+
Once you have a binding, it is possible to find all translation +units that declare or refer to that binding.
From the Syntactic view, you can ask the AST Rewriter to calculate
+the TextEdits required to accomplish changes to the AST.
+