calcite git commit: [CALCITE-2038] Fix incomplete sentence in tutorial

[mm...@apache.org]

Repository: calcite
Updated Branches:
  refs/heads/master c25f7c937 -> 93a3aaedd


[CALCITE-2038] Fix incomplete sentence in tutorial


Project: http://git-wip-us.apache.org/repos/asf/calcite/repo
Commit: http://git-wip-us.apache.org/repos/asf/calcite/commit/93a3aaed
Tree: http://git-wip-us.apache.org/repos/asf/calcite/tree/93a3aaed
Diff: http://git-wip-us.apache.org/repos/asf/calcite/diff/93a3aaed

Branch: refs/heads/master
Commit: 93a3aaeddb18078352556c5c8859b5e3cae7d482
Parents: c25f7c9
Author: Michael Mior <mm...@uwaterloo.ca>
Authored: Tue Nov 7 09:20:00 2017 -0500
Committer: Michael Mior <mm...@uwaterloo.ca>
Committed: Tue Nov 7 09:20:00 2017 -0500

----------------------------------------------------------------------
 site/_docs/tutorial.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/calcite/blob/93a3aaed/site/_docs/tutorial.md
----------------------------------------------------------------------
diff --git a/site/_docs/tutorial.md b/site/_docs/tutorial.md
index 2a6e91e..45196bb 100644
--- a/site/_docs/tutorial.md
+++ b/site/_docs/tutorial.md
@@ -464,7 +464,8 @@ with the adapter and find a more efficient way of accessing the data.
 This negotiation is a simple form of query optimization. Calcite supports query
 optimization by adding <i>planner rules</i>. Planner rules operate by
 looking for patterns in the query parse tree (for instance a project on top
-of a certain kind of table), and
+of a certain kind of table), and replacing the matched nodes in the tree by
+a new set of nodes which implement the optimization.
 
 Planner rules are also extensible, like schemas and tables. So, if you have a
 data store that you want to access via SQL, you first define a custom table or