Pair up dangling paragraph tags; Make sure all text at least in P
Closing P tags are missing or mistyped for another letter. Other chunks of text need to be wrapped in P tags to fall inline with rest of page and not run with such wild abandon.
This commit is contained in:
@@ -95,6 +95,7 @@ $ git branch
|
||||
|
||||
<p>So let's start by creating a new branch and switching to it. You can do
|
||||
that by running <code>git branch (branchname)</code>.
|
||||
</p>
|
||||
|
||||
<pre>
|
||||
$ git branch testing
|
||||
@@ -306,7 +307,7 @@ class HiWorld
|
||||
revert to what it was before I switched branches. Here I can change
|
||||
something different (in this case the printed output) and at the same
|
||||
time rename the file from <code>hello.rb</code> to <code>ruby.rb</code>.
|
||||
</b>
|
||||
</p>
|
||||
|
||||
<pre>
|
||||
<b>$ git checkout master</b>
|
||||
@@ -372,7 +373,7 @@ HiWorld.hello
|
||||
of code is edited in different branches there is no way for a computer
|
||||
to figure it out, so it's up to us. Let's see another example of changing
|
||||
the same line in two branches.
|
||||
<p>
|
||||
</p>
|
||||
|
||||
<pre>
|
||||
<b>$ git branch</b>
|
||||
@@ -504,6 +505,7 @@ M README
|
||||
<code>git log</code> when you are in that branch. For example, if we run
|
||||
<code>git log</code> in the Hello World project that we have been working
|
||||
on in this section, we'll see all the commit messages that we've done.
|
||||
</p>
|
||||
|
||||
<pre>
|
||||
<b>$ git log</b>
|
||||
|
Reference in New Issue
Block a user