commit 696d847751ec48e1f7f9847a115b5f10f32f13a0
author andybons <andybons@chromium.org> Thu Jul 30 15:38:01 2015 -0700
committer Commit bot <commit-bot@chromium.org> Thu Jul 30 22:38:44 2015 +0000
tree 8643dce97ec1f21f02ab44ace4a25dc542f47147
parent 26db28adb32c0c1321f358702125487b23579992

Clean up some typos in GN quick start page.

Also adjust the sample code a bit.

BUG=none

Review URL: https://codereview.chromium.org/1259763004

Cr-Original-Commit-Position: refs/heads/master@{#341213}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 19c81c689ac484b960dcbfb8633e1723245e5810

tools/gn/docs/quick_start.md

diff --git a/tools/gn/docs/quick_start.md b/tools/gn/docs/quick_start.md
index e6840a9..c884edb 100644
--- a/tools/gn/docs/quick_start.md
+++ b/tools/gn/docs/quick_start.md
@@ -74,7 +74,7 @@
 
 ```
 use_goma = true
-goma_dir = "~/foo/bar/goma" 
+goma_dir = "~/foo/bar/goma"
 ```
 
 If your goma is in the default location (`~/goma`) then you can omit the
@@ -105,9 +105,9 @@
 There should already be a `hello_world.cc` file in that directory,
 containing what you expect. That's it! Now we just need to tell the
 build about this file. Open the `BUILD.gn` file in the root directory
-and add the label of this target to the dependencies of the root group
-(a "group" target is a meta-target that is just a collection of other
-targets):
+and add the label of this target to the dependencies of one of the root
+groups (a "group" target is a meta-target that is just a collection of
+other targets):
 
 ```
 group("root") {
@@ -168,7 +168,7 @@
 }
 ```
 
-This executable includes one source file,and depends on the previous
+This executable includes one source file and depends on the previous
 static library. The static library is referenced by its label in the
 `deps`. You could have used the full label `//tools/gn/tutorial:hello`
 but if you're referencing a target in the same build file, you can use
@@ -183,7 +183,7 @@
 out/Default/say_hello
 ```
 
-Note that you **didn't** need to re-run GN.GN will automatically rebuild
+Note that you **didn't** need to re-run GN. GN will automatically rebuild
 the ninja files when any build file has changed. You know this happens
 when ninja prints `[1/1] Regenerating ninja files` at the beginning of
 execution.
@@ -275,7 +275,7 @@
 [1/1] Regenerating ninja files
 [4/4] LINK say_hello
 > out/Default/say_hello
-Hello, Bill and Ted.
+Hello, Bill and Joy.
 ```
 
 ## Don't know what's going on?

tools/gn/tutorial/say_hello.cc

diff --git a/tools/gn/tutorial/say_hello.cc b/tools/gn/tutorial/say_hello.cc
index 074b8b8..d8092bd 100644
--- a/tools/gn/tutorial/say_hello.cc
+++ b/tools/gn/tutorial/say_hello.cc
@@ -6,9 +6,9 @@
 
 int main() {
 #if defined(TWO_PEOPLE)
-  Hello("Bill", "Ted");
+  Hello("Bill", "Joy");
 #else
-  Hello("you guys");
+  Hello("everyone");
 #endif
   return 0;
 }