Update 2016-11-24-offline-mirror.md (#924)

Author: arcanis

_posts/2016-11-24-offline-mirror.md

@@ -100,13 +100,12 @@ $ mv ~/.yarnrc ./
 
 ### Initialize the new lockfile
 
-Remove node_modules and yarn.lock that were generated previously and run yarn install again:
+Remove the node_modules that got generated previously and run yarn install again:
 
 ```bash
 $ rm -rf node_modules/ yarn.lock
 $ yarn install
 yarn install v0.17.8
-info No lockfile found.
 [1/4] 🔍  Resolving packages...
 [2/4] 🚚  Fetching packages...
 [3/4] 🔗  Linking dependencies...
@@ -115,7 +114,7 @@ success Saved lockfile.
 ✨  Done in 0.57s.
 ```
 
-The dependency resolutions in your `yarn.lock` should look the same as the original:
+The dependency resolutions in your `yarn.lock` should look the same as the original (you shouldn't have any diff):
 
 ```yaml
 # THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
@@ -140,9 +139,9 @@ mime-types@^2.1.13:
     mime-db "~1.25.0"
 ```
 
-The offline cache filename is derived from the base name of the resolved URL. It will be stored in the npm-packages-offline-cache folder that was configured earlier. Each resolved dependency also contains a checksum after the file name to ensure that no one mangles with the downloaded files.
+The offline cache file will be stored in the npm-packages-offline-cache folder that was configured earlier. Each resolved dependency also contains a checksum after the file name to ensure that no one mangles with the downloaded files.
 
-And inside the “Offline mirror” folder we have the .tgz files that yarn will use for the following builds without reaching out to network.
+If we look inside the “Offline mirror” folder we'll see the .tgz files that yarn will use for the following builds without reaching out to network:
 
 ```bash
 $ ls npm-packages-offline-cache/