about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2014-07-17 17:16:23 +0000
committerbors <bors@rust-lang.org>2014-07-17 17:16:23 +0000
commitc4b1077dfbc835f1d1d1a9efbc9b11d6b9c0e35d (patch)
tree07dbbc85b02886ff05bae5539db8aa2972ccee05
parent92b5bf86b775b2749b2e5f4300650370052c9001 (diff)
parenta1def0856ed8c658a4985f405b1ec04eb85c4786 (diff)
downloadrust-c4b1077dfbc835f1d1d1a9efbc9b11d6b9c0e35d.tar.gz
rust-c4b1077dfbc835f1d1d1a9efbc9b11d6b9c0e35d.zip
auto merge of #15706 : phi-gamma/rust/master, r=huonw
I kept changes to each file in a separate commit. Please let me know if you prefer them
squashed!
-rw-r--r--man/rustc.12
-rw-r--r--src/doc/complement-lang-faq.md4
-rw-r--r--src/libsyntax/parse/obsolete.rs2
3 files changed, 4 insertions, 4 deletions
diff --git a/man/rustc.1 b/man/rustc.1
index f49faf2ec6e..00d698e611e 100644
--- a/man/rustc.1
+++ b/man/rustc.1
@@ -68,7 +68,7 @@ AST nodes and blocks with IDs), or flowgraph=<nodeid> (graphviz
 formatted flowgraph for node)
 .TP
 \fB\-\-dep-info\fR [FILENAME]
-Output dependency info to <filename> after compiling, in o format suitable
+Output dependency info to <filename> after compiling, in a format suitable
 for use by Makefiles.
 .TP
 \fB\-\-sysroot\fR PATH
diff --git a/src/doc/complement-lang-faq.md b/src/doc/complement-lang-faq.md
index ae58db9077c..ce037251e46 100644
--- a/src/doc/complement-lang-faq.md
+++ b/src/doc/complement-lang-faq.md
@@ -31,7 +31,7 @@ You may also be interested in browsing [GitHub's Rust][github-rust] page.
 
 ## Does it run on Windows?
 
-Yes. All development happens in lock-step on all 3 target platforms. Using MinGW, not Cygwin. Note that the windows implementation currently has some limitations: in particular 64-bit build is [not fully supported yet][win64], and all executables created by rustc [depends on libgcc DLL at runtime][libgcc].
+Yes. All development happens in lock-step on all 3 target platforms. Using MinGW, not Cygwin. Note that the windows implementation currently has some limitations: in particular 64-bit build is [not fully supported yet][win64], and all executables created by rustc [depend on libgcc DLL at runtime][libgcc].
 
 [win64]: https://github.com/rust-lang/rust/issues/1237
 [libgcc]: https://github.com/rust-lang/rust/issues/11782
@@ -68,7 +68,7 @@ Cleanup through RAII-style destructors is more likely to work than in catch bloc
 
 ## Why aren't modules type-parametric?
 
-We want to maintain the option to parametrize at runtime. We may make eventually change this limitation, but initially this is how type parameters were implemented.
+We want to maintain the option to parametrize at runtime. We may eventually change this limitation, but initially this is how type parameters were implemented.
 
 ## Why aren't values type-parametric? Why only items?
 
diff --git a/src/libsyntax/parse/obsolete.rs b/src/libsyntax/parse/obsolete.rs
index cadae7ef12f..ba401d313d8 100644
--- a/src/libsyntax/parse/obsolete.rs
+++ b/src/libsyntax/parse/obsolete.rs
@@ -76,7 +76,7 @@ impl<'a> ParserObsoleteMethods for parser::Parser<'a> {
             ),
             ObsoleteManagedExpr => (
                 "`@` notation for a managed pointer allocation",
-                "use the `box(GC)` oeprator instead of `@`"
+                "use the `box(GC)` operator instead of `@`"
             ),
         };