diff --git a/basic/index.html b/basic/index.html
index 9a2f3d3..23455c8 100644
--- a/basic/index.html
+++ b/basic/index.html
@@ -612,7 +612,7 @@ <h2>
 
     <h4>
       git reset HEAD
-      <small>undo the last commit and unstage the files</small>
+      <small>unstage files from index and reset pointer to HEAD</small>
     </h4>
 
     <p>First, you can use it to unstage something that has been
@@ -691,7 +691,7 @@ <h4>
 
     <h4>
       git reset --soft
-      <small>undo the last commit</small>
+      <small>moves HEAD to specified commit reference, index and staging are untouched</small>
     </h4>
 
     <p>The first thing <code>git reset</code> does is undo the last
@@ -721,11 +721,12 @@ <h4>
 
     <h4>
       git reset --hard
-      <small>undo the last commit, unstage files AND undo any changes in the working directory</small>
+      <small>unstage files AND undo any changes in the working directory since last commit</small>
     </h4>
 
     <p>The third option is to go <code>--hard</code> and make your working
-       directory look like the index, unstage files and undo the last commit.
+       directory look like the index, unstage files and undo any changes made
+       since the last commit.
        This is the most dangerous option and not working directory safe. Any
        changes not in the index or have not been commited will be lost.</p>
 
@@ -752,7 +753,8 @@ <h4>
 
     <p>In the above example, while we had both changes ready to commit and
        ready to stage, a <code>git reset --hard</code> wiped them out.
-       On top of that, the last commit has been undone.</p>
+       The working tree and staging area are reset to the tip of the current
+       branch or HEAD.</p>
 
     <p>You can replace <code>HEAD</code> with a commit SHA-1 or another
     parent reference to reset to that specific point.</p>