reworded explanation of running code and explaining comments in re learnco students issue #2

Author: tkoar

README.md

@@ -29,20 +29,19 @@ For example, let's say we want to capitalize all of the letters of "art vandlay"
 
 
 ```python
-"art vandelay" # 'ART VANDELAY'
+"art vandelay"
 ```
 
 Notice that there is no output below the gray code above.  This is because Jupyter notebooks do not automatically run our code - so they do not automatically know the output.  To display the output, we must **run** the code by clicking on the gray cell and then pressing shift + enter.  Let's try it in the cell above and see our output appear below.
 
-Ok, once we see the output take a look at the hash tag to the right of the string.  The hash tag to the right is a comment.  Comments are used for programmers to annotate their code, but a comment has no impact on the code.  See this by running the next cell below (again, press shift + enter).
+Ok, once we see the output take a look at the cell below with the hash tag to the right of the string, `'hello'`.  This is a comment.  Comments are used for programmers to annotate their code, but a comment has no impact on the code.  See this by running the cell below (again, press shift + enter).
 
 
 ```python
-'hello'
-### whattttt
+'hello' ### whattttt
 ```
 
-If we press shift+enter on the cell above to run the code, we will see that Python happily ignores the comment.  So here (and in future labs), a comment will be provided to indicate what we should see as the return value of our code.  When we press shift+enter, and the output below matches the comment to the right of our code, we did it correctly.
+After pressing shift+enter on the cell above, we see that Python happily ignores the comment. So here (and in future labs), a comment will be provided to indicate what we should see as the return value of our code. When we press shift+enter, and the output below matches the comment to the right of our code, we did it correctly.
 
 > In future labs, Learn will check our code to ensure that we did it correctly.  But for our first lab, this works fine.
 

index.ipynb

@@ -86,7 +86,7 @@
    },
    "outputs": [],
    "source": [
-    "\"art vandelay\" # 'ART VANDELAY'"
+    "\"art vandelay\""
    ]
   },
   {
@@ -100,7 +100,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Ok, once we see the output take a look at the hash tag to the right of the string.  The hash tag to the right is a comment.  Comments are used for programmers to annotate their code, but a comment has no impact on the code.  See this by running the next cell below (again, press shift + enter)."
+    "Ok, once we see the output take a look at the cell below with the hash tag to the right of the string, `'hello'`.  This is a comment.  Comments are used for programmers to annotate their code, but a comment has no impact on the code.  See this by running the cell below (again, press shift + enter)."
    ]
   },
   {
@@ -111,15 +111,14 @@
    },
    "outputs": [],
    "source": [
-    "'hello'\n",
-    "### whattttt"
+    "'hello' ### whattttt"
    ]
   },
   {
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "If we press shift+enter on the cell above to run the code, we will see that Python happily ignores the comment.  So here (and in future labs), a comment will be provided to indicate what we should see as the return value of our code.  When we press shift+enter, and the output below matches the comment to the right of our code, we did it correctly."
+    "After pressing shift+enter on the cell above, we see that Python happily ignores the comment. So here (and in future labs), a comment will be provided to indicate what we should see as the return value of our code. When we press shift+enter, and the output below matches the comment to the right of our code, we did it correctly."
    ]
   },
   {