Deployed 63c4de3 to prerelease with MkDocs 1.5.3 and mike 2.0.0

prerelease/git-comparison/index.html

@@ -1257,10 +1257,11 @@ various use cases.</p>
 <li><strong>The working copy is automatically committed.</strong> That results in a simpler and
   more consistent CLI because the working copy is now treated like any other
   commit. <a href="../working-copy/">Details</a>.</li>
-<li><strong>There's no index (staging area).</strong> That also results in a simpler
-  CLI for similar reasons. The index is very similar to an intermediate commit
-  between <code>HEAD</code> and the working copy, so workflows that depend on it can be
-  modeled using proper commits instead. <a href="#the-index">Details</a>.</li>
+<li><strong>There's no index (staging area).</strong> Because the working copy is automatically
+  committed, an index-like concept doesn't make sense. The index is very similar
+  to an intermediate commit between <code>HEAD</code> and the working copy, so workflows
+  that depend on it can be modeled using proper commits instead. Jujutsu has
+  excellent support for moving changes between commits. <a href="#the-index">Details</a>.</li>
 <li><strong>No need for branch names (but they are supported).</strong> Git lets you check out
   a commit without attaching a branch. It calls this state "detached HEAD". This
   is the normal state in Jujutsu (there's actually no way -- yet, at least -- to