Fix some typos
lintian (a debian package helper) showed the following
spelling-errors:
ribalda@alco:/tmp/gn-debian (master *%)$ lintian ../generate-ninja_0.0~git20201124.53d9201-1.1*changes --pedantic --display-info --display-experimental --no-tag-display-limit
I: generate-ninja: spelling-error-in-binary usr/bin/gn "allows to" "allows one to"
I: generate-ninja: spelling-error-in-binary usr/bin/gn Verfication Verification
I: generate-ninja: spelling-error-in-binary usr/bin/gn appropiate appropriate
I: generate-ninja: spelling-error-in-binary usr/bin/gn defaut default
I: generate-ninja: spelling-error-in-binary usr/bin/gn dependant dependent
I: generate-ninja: spelling-error-in-binary usr/bin/gn occurence occurrence
I: generate-ninja: spelling-error-in-binary usr/bin/gn ouput output
I: generate-ninja: spelling-error-in-binary usr/bin/gn ouputs outputs
I: generate-ninja: spelling-error-in-binary usr/bin/gn overriden overridden
First seen at: https://salsa.debian.org/debian/gn/-/blob/eb11997ea5fb2165ebe8af52e1f44eaf0c364b78/debian/patches/Fix-spelling-error.patch
Change-Id: I68f69d5bfad68e5a1e9c80081d131c129a1861a5
Reviewed-on: https://gn-review.googlesource.com/c/gn/+/11020
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
diff --git a/docs/reference.md b/docs/reference.md
index 80151ba..ec19bfd 100644
--- a/docs/reference.md
+++ b/docs/reference.md
@@ -812,7 +812,7 @@
```
--xcode-project=<file_name>
- Override defaut Xcode project file name ("all"). The project file is
+ Override default Xcode project file name ("all"). The project file is
written to the root build directory.
--xcode-build-system=<value>
@@ -1471,7 +1471,7 @@
### <a name="func_bundle_data"></a>**bundle_data**: [iOS/macOS] Declare a target without output.
```
- This target type allows to declare data that is required at runtime. It is
+ This target type allows one to declare data that is required at runtime. It is
used to inform "create_bundle" targets of the files to copy into generated
bundle, see "gn help create_bundle" for help.
@@ -3881,7 +3881,7 @@
The Swift tool has multiple input and outputs. It must have exactly one
output of .swiftmodule type, but can have one or more object file outputs,
- in addition to other type of ouputs. The following expansions are available:
+ in addition to other type of outputs. The following expansions are available:
{{module_name}}
Expands to the string representing the module name of target under
@@ -4225,7 +4225,7 @@
This is value is exposed so that cross-compile toolchains can access the host
architecture when needed.
- The value should generally be considered read-only, but it can be overriden
+ The value should generally be considered read-only, but it can be overridden
in order to handle unusual cases where there might be multiple plausible
values for the host architecture (e.g., if you can do either 32-bit or 64-bit
builds). The value is not used internally by GN for any purpose.
@@ -4561,7 +4561,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -4667,7 +4667,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -4702,7 +4702,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -4881,7 +4881,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -4915,7 +4915,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -4949,7 +4949,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -4983,7 +4983,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5017,7 +5017,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5179,7 +5179,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5247,7 +5247,7 @@
Options for this field are "cdylib", "staticlib", "proc-macro", and "dylib".
This field sets the `crate-type` attribute for the `rustc` tool on static
- libraries, as well as the appropiate output extension in the
+ libraries, as well as the appropriate output extension in the
`rust_output_extension` attribute. Since outputs must be explicit, the `lib`
crate type (where the Rust compiler produces what it thinks is the
appropriate library type) is not supported.
@@ -5344,7 +5344,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5472,7 +5472,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5504,7 +5504,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5597,7 +5597,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5705,7 +5705,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5738,7 +5738,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5801,7 +5801,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -5828,7 +5828,7 @@
Generally, these keys will include three types of lists: lists of ordinary
strings, lists of filenames intended to be rebased according to their
particular source directory, and lists of target labels intended to be used
- as barriers to the walk. Verfication of these categories occurs at walk time,
+ as barriers to the walk. Verification of these categories occurs at walk time,
not creation time (since it is not clear until the walk which values are
intended for which purpose).
```
@@ -6178,7 +6178,7 @@
```
Public configs are applied to all targets that depend directly on this one.
- These dependant targets can further push this target's public configs
+ These dependent targets can further push this target's public configs
higher in the dependency tree by depending on it via public_deps (see "gn
help public_deps").
@@ -6247,7 +6247,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -6427,7 +6427,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -6547,7 +6547,7 @@
those configs appear in the list.
5. all_dependent_configs pulled from dependencies, in the order of
the "deps" list. This is done recursively. If a config appears
- more than once, only the first occurence will be used.
+ more than once, only the first occurrence will be used.
6. public_configs pulled from dependencies, in the order of the
"deps" list. If a dependency is public, they will be applied
recursively.
@@ -6788,7 +6788,7 @@
default_args [optional]
Scope containing the default overrides for declared arguments. These
overrides take precedence over the default values specified in the
- declare_args() block, but can be overriden using --args or the
+ declare_args() block, but can be overridden using --args or the
args.gn file.
This is intended to be used when subprojects declare arguments with
diff --git a/src/gn/bundle_data_target_generator.cc b/src/gn/bundle_data_target_generator.cc
index eb7e679..0246cff 100644
--- a/src/gn/bundle_data_target_generator.cc
+++ b/src/gn/bundle_data_target_generator.cc
@@ -36,7 +36,7 @@
}
if (target_->action_values().outputs().list().size() != 1) {
*err_ = Err(
- function_call_, "Target bundle_data must have exactly one ouput.",
+ function_call_, "Target bundle_data must have exactly one output.",
"You must specify exactly one value in the \"output\" array for the"
"destination\ninto the generated bundle (see \"gn help bundle_data\"). "
"If there are multiple\nsources to copy, use source expansion (see "
diff --git a/src/gn/command_gen.cc b/src/gn/command_gen.cc
index 20bc332..e5248b9 100644
--- a/src/gn/command_gen.cc
+++ b/src/gn/command_gen.cc
@@ -494,7 +494,7 @@
Xcode Flags
--xcode-project=<file_name>
- Override defaut Xcode project file name ("all"). The project file is
+ Override default Xcode project file name ("all"). The project file is
written to the root build directory.
--xcode-build-system=<value>
diff --git a/src/gn/function_toolchain.cc b/src/gn/function_toolchain.cc
index 693fb65..a6deec6 100644
--- a/src/gn/function_toolchain.cc
+++ b/src/gn/function_toolchain.cc
@@ -792,7 +792,7 @@
The Swift tool has multiple input and outputs. It must have exactly one
output of .swiftmodule type, but can have one or more object file outputs,
- in addition to other type of ouputs. The following expansions are available:
+ in addition to other type of outputs. The following expansions are available:
{{module_name}}
Expands to the string representing the module name of target under
diff --git a/src/gn/functions_target.cc b/src/gn/functions_target.cc
index 7693369..d781fd5 100644
--- a/src/gn/functions_target.cc
+++ b/src/gn/functions_target.cc
@@ -278,7 +278,7 @@
const char kBundleData_Help[] =
R"(bundle_data: [iOS/macOS] Declare a target without output.
- This target type allows to declare data that is required at runtime. It is
+ This target type allows one to declare data that is required at runtime. It is
used to inform "create_bundle" targets of the files to copy into generated
bundle, see "gn help create_bundle" for help.
diff --git a/src/gn/metadata.h b/src/gn/metadata.h
index 2e2b742..d8298e8 100644
--- a/src/gn/metadata.h
+++ b/src/gn/metadata.h
@@ -19,7 +19,7 @@
// Generally, these keys will include three categories of strings: ordinary
// strings, filenames intended to be rebased according to their particular
// source directory, and target labels intended to be used as barriers to the
-// walk. Verfication of these categories occurs at walk time, not creation
+// walk. Verification of these categories occurs at walk time, not creation
// time (since it is not clear until the walk which values are intended for
// which purpose).
//
diff --git a/src/gn/rust_variables.cc b/src/gn/rust_variables.cc
index a23ac66..651eb07 100644
--- a/src/gn/rust_variables.cc
+++ b/src/gn/rust_variables.cc
@@ -65,7 +65,7 @@
Options for this field are "cdylib", "staticlib", "proc-macro", and "dylib".
This field sets the `crate-type` attribute for the `rustc` tool on static
- libraries, as well as the appropiate output extension in the
+ libraries, as well as the appropriate output extension in the
`rust_output_extension` attribute. Since outputs must be explicit, the `lib`
crate type (where the Rust compiler produces what it thinks is the
appropriate library type) is not supported.
diff --git a/src/gn/setup.cc b/src/gn/setup.cc
index 5ef4346..b6fdee2 100644
--- a/src/gn/setup.cc
+++ b/src/gn/setup.cc
@@ -148,7 +148,7 @@
default_args [optional]
Scope containing the default overrides for declared arguments. These
overrides take precedence over the default values specified in the
- declare_args() block, but can be overriden using --args or the
+ declare_args() block, but can be overridden using --args or the
args.gn file.
This is intended to be used when subprojects declare arguments with
diff --git a/src/gn/source_dir.h b/src/gn/source_dir.h
index 9dd847c..5c436f4 100644
--- a/src/gn/source_dir.h
+++ b/src/gn/source_dir.h
@@ -51,7 +51,7 @@
const std::string_view& source_root = std::string_view(),
const std::string* v_value = nullptr) const;
- // Like ResolveRelativeAs above, but allows to produce result
+ // Like ResolveRelativeAs above, but allows one to produce result
// without overhead for string conversion (on input value).
template <typename StringType>
std::string ResolveRelativeAs(
diff --git a/src/gn/variables.cc b/src/gn/variables.cc
index 77f7ba7..d5c5e45 100644
--- a/src/gn/variables.cc
+++ b/src/gn/variables.cc
@@ -33,7 +33,7 @@
This is value is exposed so that cross-compile toolchains can access the host
architecture when needed.
- The value should generally be considered read-only, but it can be overriden
+ The value should generally be considered read-only, but it can be overridden
in order to handle unusual cases where there might be multiple plausible
values for the host architecture (e.g., if you can do either 32-bit or 64-bit
builds). The value is not used internally by GN for any purpose.
@@ -411,7 +411,7 @@
" those configs appear in the list.\n" \
" 5. all_dependent_configs pulled from dependencies, in the order of\n" \
" the \"deps\" list. This is done recursively. If a config appears\n" \
- " more than once, only the first occurence will be used.\n" \
+ " more than once, only the first occurrence will be used.\n" \
" 6. public_configs pulled from dependencies, in the order of the\n" \
" \"deps\" list. If a dependency is public, they will be applied\n" \
" recursively.\n"
@@ -1431,7 +1431,7 @@
Generally, these keys will include three types of lists: lists of ordinary
strings, lists of filenames intended to be rebased according to their
particular source directory, and lists of target labels intended to be used
- as barriers to the walk. Verfication of these categories occurs at walk time,
+ as barriers to the walk. Verification of these categories occurs at walk time,
not creation time (since it is not clear until the walk which values are
intended for which purpose).
@@ -1800,7 +1800,7 @@
Propagation of public configs
Public configs are applied to all targets that depend directly on this one.
- These dependant targets can further push this target's public configs
+ These dependent targets can further push this target's public configs
higher in the dependency tree by depending on it via public_deps (see "gn
help public_deps").
