@@ -19 +19 @@ Index: publish/quick-start.html
-+    <a href="#understanding-the-terms">Understanding the terms</a>
++    <a href="#terminology">Terminology</a>
@@ -59 +59 @@ Index: publish/quick-start.html
-+      Install the <tt>svn</tt> client to start collaborating on the project
++      Install the <tt>svn</tt> client to start collaborating on a project
@@ -100 +100 @@ Index: publish/quick-start.html
-+  <div class="h2" id="understanding-the-terms">
++  <div class="h2" id="terminology">
@@ -102,2 +102,2 @@ Index: publish/quick-start.html
-+      Understanding the terms
-+      <a class="sectionlink" href="#understanding-the-terms"
++      Terminology
++      <a class="sectionlink" href="#terminology"
@@ -114,4 +114,5 @@ Index: publish/quick-start.html
-+        server and is usually exposed either by Apache HTTP Server
-+        (mod_dav_svn) or svnserve server.  The repository acts as a single
-+        source of truth and – as a central storage – it contains the complete
-+        history of changes of the versioned data in form of revisions.
++        server and is usually exposed either by an Apache HTTP Server
++        (through the <tt>mod_dav_svn</tt> module) or by an svnserve server.
++        The repository acts as a single source of truth and – as a central
++        storage – it contains the complete history of changes of the versioned
++        data in form of revisions.
@@ -127 +128 @@ Index: publish/quick-start.html
-+          svnserve: <tt>svn://svn.example.com/repos/MyRepo/MyProject/trunk</tt>
++          svnserve: <tt>svn://svn.example.com/repos/MyRepo/MyProject/branches/MyBranch</tt>
@@ -130 +131 @@ Index: publish/quick-start.html
-+          Direct access (Unix-style): <tt>file://var/svn/repos/MyRepo/MyProject/trunk</tt>
++          Direct access (Unix-style): <tt>file://var/svn/repos/MyRepo/MyProject/tags/1.1.0</tt>
@@ -133 +134 @@ Index: publish/quick-start.html
-+          Direct access (Windows-style): <tt>file:///C:/Repositories/MyRepo/MyProject/trunk</tt>
++          Direct access (Windows-style): <tt>file:///C:/Repositories/MyRepo/trunk/MyProject</tt>
@@ -154 +155,4 @@ Index: publish/quick-start.html
-+        regular directory with version-control capabilities.
++        regular directory with version-control capabilities.  A working copy
++        has an administrative directory named <tt>.svn</tt> at its root.  The
++        administrative directory contains metadata necessary for Subversion to
++        manage the version-control capabilities.
@@ -176 +180 @@ Index: publish/quick-start.html
-+        In case you want to import an existing non-versioned data to SVN
++        In case you want to import existing non-versioned data into an SVN
@@ -217 +221 @@ Index: publish/quick-start.html
-+$ svn checkout https://svn.example.com/repos/MyRepo/MyProject/trunk
++$ svn checkout https://svn.example.com/repos/MyRepo/MyProject/trunk MyWorkingCopy
@@ -222 +226 @@ Index: publish/quick-start.html
-+        will be located in MyProject directory on your computer.  Note that
++        will be located in MyWorkingCopy directory on your computer.  Note that
@@ -253,2 +257,2 @@ Index: publish/quick-start.html
-+        It is a rule to update your working copy before committing local
-+        modifications to the repository.
++        It is a good practice to update your working copy before committing
++        local modifications to the repository.
@@ -267 +271 @@ Index: publish/quick-start.html
-+        thoroughly, you are ready to publish them to the central repository.
++        thoroughly, you are ready to commit them to the central repository.
@@ -309,4 +313,5 @@ Index: publish/quick-start.html
-+            Note the <tt>-m (--message)</tt> option. You must always include
-+            descriptive commit log message.  The log message has to help others
-+            to understand why you made this commit, it has to contain a summary
-+            of the changes you made.
++            Note the <tt>-m (--message)</tt> option. You should always include
++            a descriptive commit log message.  It should help others including
++            yourself understand the reason why you made this commit.  It is a
++            good idea to include a summary of your changes in the log message,
++            too.
@@ -316 +321 @@ Index: publish/quick-start.html
-+    <div class="h3" id="performing-file-operations">
++    <div class="h3" id="performing-file-and-dir-operations">
@@ -318,2 +323,2 @@ Index: publish/quick-start.html
-+        Performing file operations
-+        <a class="sectionlink" href="#performing-file-operations"
++        Performing file and directory operations
++        <a class="sectionlink" href="#performing-file-and-dir-operations"
@@ -328 +333,8 @@ Index: publish/quick-start.html
-+      <div class="h4" id="adding-new-files">
++      <p>
++        Subversion does not use heurisic-tracking for tree changes in a working
++        copy. Subversion requires explicit tracking of tree changes.  If you
++        perform a tree changes such as move or copy with regular filesystem
++        commands, Subversion will not know about this operation.  To track tree
++        changes Subversion should be made aware of them.
++      </p>
++      <div class="h4" id="adding-new-files-and-directories">
@@ -330,2 +342,2 @@ Index: publish/quick-start.html
-+          Adding new files
-+          <a class="sectionlink" href="#adding-new-files"
++          Adding new files and directories
++          <a class="sectionlink" href="#adding-new-files-and-directories"
@@ -335,2 +347,2 @@ Index: publish/quick-start.html
-+          Put new files to the working copy and Subversion will recognize them
-+          as unversioned.  It will not automatically start tracking the new
++          Put new files or directories to the working copy and Subversion will
++          see them as "unversioned".  It will not automatically start tracking the new
@@ -401 +413 @@ Index: publish/quick-start.html
-+          Revert your local uncommitted changes using the
++          Discard your local uncommitted changes using the
@@ -426 +438,2 @@ Index: publish/quick-start.html
-+        working copy and in the repository.
++        working copy and in the repository when you want them to be
++        historically related.
@@ -429,4 +442,4 @@ Index: publish/quick-start.html
-+        The command <tt>svn copy</tt> is used for branching because, branch is
-+        technically a copy of the source you copy from.  However, this is not
-+        an ordinary copy are familiar with when copying files on your local
-+        file system.  Branches in Subversion are so called
++        The command <tt>svn copy</tt> is used for branching because branch is
++        technically a copy of the source you copy from.  However, it is not
++        an ordinary copy that you are familiar with when copying files on your
++        local file system.  Branches in Subversion repositories are so called
@@ -455,16 +467,0 @@ Index: publish/quick-start.html
-+      <div class="h4" id="WC-copy">
-+        <h4>
-+          Creating a branch through a working copy
-+          <a class="sectionlink" href="#WC-copy"
-+             title="Link to this section">&para;</a>
-+        </h4>
-+        <p>
-+          When you interact with the remote central repository using your
-+          private local workspace - the working copy - you can use
-+          repository-relative URL instead of direct URL to URL copy to create
-+          a new branch:
-+        </p>
-+<pre>
-+$ svn copy "^/MyRepo/trunk" "^/MyRepo/branches/MyNewBranch" -m "Creating a new branch"
-+</pre>
-+      </div>