about summary refs log tree commit diff
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2015-09-24 07:43:37 +0200
committerTshepang Lekhonkhobe <tshepang@gmail.com>2015-09-24 07:43:37 +0200
commit16244b884dd7716fbab8e7cd8a235567cee46229 (patch)
treeb1115dd8dbf6b2986080c29c59d0def54589872e
parent07ca1ab1ec32ac99a61312ec07d66db5f3657040 (diff)
downloadrust-16244b884dd7716fbab8e7cd8a235567cee46229.tar.gz
rust-16244b884dd7716fbab8e7cd8a235567cee46229.zip
reference: make that less awkward to read
-rw-r--r--src/doc/reference.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/reference.md b/src/doc/reference.md
index 83849574260..f187986ffb7 100644
--- a/src/doc/reference.md
+++ b/src/doc/reference.md
@@ -3935,7 +3935,7 @@ found in the [ffi section of the book][ffi].
 
 In one session of compilation, the compiler can generate multiple artifacts
 through the usage of either command line flags or the `crate_type` attribute.
-If one or more command line flag is specified, all `crate_type` attributes will
+If one or more command line flags are specified, all `crate_type` attributes will
 be ignored in favor of only building the artifacts specified by command line.
 
 * `--crate-type=bin`, `#[crate_type = "bin"]` - A runnable executable will be
@@ -3981,7 +3981,7 @@ Note that these outputs are stackable in the sense that if multiple are
 specified, then the compiler will produce each form of output at once without
 having to recompile. However, this only applies for outputs specified by the
 same method. If only `crate_type` attributes are specified, then they will all
-be built, but if one or more `--crate-type` command line flag is specified,
+be built, but if one or more `--crate-type` command line flags are specified,
 then only those outputs will be built.
 
 With all these different kinds of outputs, if crate A depends on crate B, then