docs: less confusing sentence for running `gclient sync` command

docs/ios_build_instructions.md

 # iOS Build Instructions
 
 **Note:** Upstreaming of iOS code is still a work in progress. In particular,
 note that **it is not currently possible to build an actual Chromium app.**
 Currently, the buildable binaries are ios\_web\_shell (a minimal wrapper around
 the web layer), and various unit tests.
 
 ## Prerequisites
 
 *   A Mac with a version of OS X capable of running the latest version
@@ skipping 23 matching lines @@
 
 ```shell
 cat > chromium.gyp_env <<EOF
 {
   "GYP_DEFINES": "OS=ios chromium_ios_signing=0",
   "GYP_GENERATORS": "ninja,xcode-ninja",
 }
 EOF
 ```
 
 Also, you should [install API

[tfarina, 2016/03/04 21:03:27]

Another question: here we say "should". But should we say that?

Is it really required? It won't build if the api-keys are not installed?

mac has a much less strong wording here: "you may want to install API keys..."
though.

 keys](https://www.chromium.org/developers/how-tos/api-keys).
 
 ## Getting the Code
 
 Next, [check out the
 code](https://www.chromium.org/developers/how-tos/get-the-code), with:
 
 ```shell
 fetch ios
 ```
@@ skipping 30 matching lines @@
 
 To run in the simulator from the command line, you can use `iossim`. For
 example, to run a debug build of ios\_web\_shell:
 
 ```shell
 out/Debug-iphonesimulator/iossim out/Debug-iphonesimulator/ios_web_shell.app
 ```
 
 ## Converting an existing Mac checkout into an iOS checkout
 
-If you want to convert your Mac checkout into an iOS checkout, you can
-follow those steps:
+If you want to convert your Mac checkout into an iOS checkout, follow the steps
+below:
 
-1. Add `target_os = [ "ios" ]` to the bottom of your `chromium/.gclient`
+1.  Add `target_os = [ "ios" ]` to the bottom of your `chromium/.gclient`
 file.
 
-2. Make sure you have the following in your `chromium/chromium.gyp_env`
+1.  Make sure you have the following in your `chromium/chromium.gyp_env`
 file (removing the `chromium_ios_signing=0` if you want to make
 developer-signed builds):
 
 ```json
 {
   "GYP_DEFINES" : "OS=ios chromium_ios_signing=0",
   "GYP_GENERATORS" : "ninja,xcode-ninja",
 }
 ```
 
-Then make sure you sync again to get all the new files like the following. At
-the end it will run `build/gyp_chromium` which will regenerate all the build
-files according to the new settings.
+1.  Make sure to sync again to fetch the iOS specific dependencies and

[tfarina, 2016/03/04 20:59:00]

Looking at the result [1], it now shows 1., 2., 1., which is bad. Sorry for not
previewing it before :/

Either we make 1., 2., 3., or just remove the number here.

What is your preference Sylvain?

[1] -
https://chromium.googlesource.com/chromium/src/+/master/docs/ios_build_instru...

+regenerate build rules using:
 
 ```shell
 gclient sync
 ```
 
 ## Troubleshooting
 
 If your build fails, check the iOS columns of [the Mac
-waterfall](http://build.chromium.org/p/chromium.mac/console) (the last
-two) to see if the bots are green. In general they should be, since
-failures on those bots will close the tree.
+waterfall](http://build.chromium.org/p/chromium.mac/console) (the last two) to
+see if the bots are green. In general they should be, since failures on those
+bots will close the tree.