@@ -1754,6 +1754,6 @@ FROM ubuntu

 RUN echo moo > oink

 # Will output something like ===> 695d7793cbe4

-# You᾿ll now have two images, 907ad6c2736f with /bar, and 695d7793cbe4 with

+# You'll now have two images, 907ad6c2736f with /bar, and 695d7793cbe4 with

 # /oink.

 ```

@@ -262,7 +262,7 @@ Successfully built 377c409b35e4

 This sends the URL `http://server/ctx.tar.gz` to the Docker daemon, which

 downloads and extracts the referenced tarball. The `-f ctx/Dockerfile`

 parameter specifies a path inside `ctx.tar.gz` to the `Dockerfile` that is used

-to build the image. Any `ADD` commands in that `Dockerfile` that refer to local

+to build the image. Any `ADD` commands in that `Dockerfile` that refers to local

 paths must be relative to the root of the contents inside `ctx.tar.gz`. In the

 example above, the tarball contains a directory `ctx/`, so the `ADD

 ctx/container.cfg /` operation works as expected.

@@ -30,7 +30,7 @@ reopened when the necessary information is provided.

 ### 2. Classify the Issue

-An issue can have multiple of the following labels. Typically, a properly classified issues should

+An issue can have multiple of the following labels. Typically, a properly classified issue should

 have:

 - One label identifying its kind (`kind/*`).

@@ -129,4 +129,4 @@ following labels to indicate their degree of priority (from more urgent to less

 | priority/P2 | Normal priority: default priority applied.                                                                                        |

 | priority/P3 | Best effort: those are nice to have / minor issues.                                                                               |

-And that's it. That should be all the information required for a new or existing contributor to come in an resolve an issue.

+And that's it. That should be all the information required for a new or existing contributor to come in a resolve an issue.

@@ -30,7 +30,7 @@ docker run --rm -it --privileged \

 Sh\*t happens. We know. Below are steps to get out of any "hash-sum mismatch" or

 "gpg sig error" or the likes error that might happen to the apt repo.

-**NOTE:** These are apt repo specific, have had no experimence with anything similar

+**NOTE:** These are apt repo specific, have had no experience with anything similar

 happening to the yum repo in the past so you can rest easy.

 For each step listed below, move on to the next if the previous didn't work.