Fix some typos in GN documentation.
Review URL: https://codereview.chromium.org/1338003005
Cr-Original-Commit-Position: refs/heads/master@{#348497}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 91e3ca5ba9866da089ef6b37fdba3d84f7e51602
diff --git a/tools/gn/docs/language.md b/tools/gn/docs/language.md
index 3aabd79..080fe49 100644
--- a/tools/gn/docs/language.md
+++ b/tools/gn/docs/language.md
@@ -56,7 +56,7 @@
The variable `sources` has a special rule: when assigning to it, a list
of exclusion patterns is applied to it. This is designed to
automatically filter out some types of files. See `gn help
-set_sources_assignment_filter` and `gn help patterns` for more.
+set_sources_assignment_filter` and `gn help label_pattern` for more.
### Strings
@@ -246,7 +246,7 @@
When loading a build file, if it doesn't exist in the given location
relative to the source root, GN will look in the secondary tree in
-`tools/gn/secondary`. This structure of this tree mirrors the main
+`tools/gn/secondary`. The structure of this tree mirrors the main
repository and is a way to add build files for directories that may be
pulled from other repositories where we can't easily check in BUILD
files.
@@ -260,7 +260,7 @@
"//base/test:test_support(//build/toolchain/win:msvc)"
```
-In this case it will look for the a toolchain definition called "msvc"
+In this case it will look for the toolchain definition called "msvc"
in the file `//build/toolchain/win` to know how to compile this target.
If you want to refer to something in the same buildfile, you can omit
@@ -380,7 +380,6 @@
preferrable over a real static library since it will build faster).
* `static_library`: A .lib or .a file (normally you'll want a
source\_set instead).
- * `test`: Generates an executable but annotates it as a test.
You can extend this to make custom target types using templates (see below).
@@ -672,7 +671,8 @@
inputs for custom target types, and to automatically remove files from
the `sources` variable (see `gn help set_sources_assignment_filter`).
-They are like simple regular expressions. See `gn help patterns` for more.
+They are like simple regular expressions. See `gn help label_pattern`
+for more.
### Executing scripts
diff --git a/tools/gn/docs/reference.md b/tools/gn/docs/reference.md
index a510d5a..8e4970d 100644
--- a/tools/gn/docs/reference.md
+++ b/tools/gn/docs/reference.md
@@ -2157,8 +2157,8 @@
have globally unique names, or you will get collisions.
Access the invoking name in your template via the implicit
- "target_name" variable. This should also be the basis of how other
- targets that a template expands to to ensure uniquness.
+ "target_name" variable. This should also be the basis for how other
+ targets that a template expands to ensure uniqueness.
A typical example would be a template that defines an action to
generate some source files, and a source_set to compile that source.
diff --git a/tools/gn/function_template.cc b/tools/gn/function_template.cc
index 290eb78..17dda06 100644
--- a/tools/gn/function_template.cc
+++ b/tools/gn/function_template.cc
@@ -72,8 +72,8 @@
" have globally unique names, or you will get collisions.\n"
"\n"
" Access the invoking name in your template via the implicit\n"
- " \"target_name\" variable. This should also be the basis of how other\n"
- " targets that a template expands to to ensure uniquness.\n"
+ " \"target_name\" variable. This should also be the basis for how other\n"
+ " targets that a template expands to ensure uniqueness.\n"
"\n"
" A typical example would be a template that defines an action to\n"
" generate some source files, and a source_set to compile that source.\n"
