itsscb/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo.git synced 2025-09-28 11:20:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

auto merge of #989 : jbcrail/cargo/fix-doc-spelling, r=steveklabnik

Browse Source 
I just made minor corrections.
This commit is contained in:
bors 2014-12-08 19:36:21 +00:00
commit 2be8559b4c
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/doc/build-script.md
View File

@ -27,7 +27,7 @@ Some example use cases of the build command are:
* Building a bundled C library. * Building a bundled C library.
* Finding a C library on the host system. * Finding a C library on the host system.
* Generating a Rust module from a specification. * Generating a Rust module from a specification.
* Performing any platform-specific configuration neeeded for the crate. * Performing any platform-specific configuration needed for the crate.
Each of these use cases will be detailed in full below to give examples of how Each of these use cases will be detailed in full below to give examples of how
the build command works. the build command works.
@ -203,7 +203,7 @@ authors = ["you@example.com"]
build = "build.rs" build = "build.rs"
``` ```
Here we can se we've got a build script specified which we'll use to generate Here we can see we've got a build script specified which we'll use to generate
some code. Let's see what's inside the build script: some code. Let's see what's inside the build script:
```rust,no_run ```rust,no_run
@ -225,10 +225,10 @@ fn main() {
There's a couple of points of note here: There's a couple of points of note here:
* The script uses the `OUT_DIR` environment variable to discover where the ouput * The script uses the `OUT_DIR` environment variable to discover where the
files should be located. It can use the process's current working directory to output files should be located. It can use the process's current working
find where the input files should be located, but in this case we don't have directory to find where the input files should be located, but in this case we
any input files. don't have any input files.
* This script is relatively simple as it just writes out a small generated file. * This script is relatively simple as it just writes out a small generated file.
One could imagine that other more fanciful operations could take place such as One could imagine that other more fanciful operations could take place such as
generating a Rust module from a C header file or another language definition, generating a Rust module from a C header file or another language definition,

2
src/doc/guide.md
View File

@ -245,7 +245,7 @@ rev = "bf739419e2d31050615c1ba1a395b474269a4"
Now, our builds will be the same. But, there's a big drawback: now we have to Now, our builds will be the same. But, there's a big drawback: now we have to
manually think about SHA-1s every time we want to update our library. This is manually think about SHA-1s every time we want to update our library. This is
both tedius and error prone. both tedious and error prone.
Enter the `Cargo.lock`. Because of its existence, we don't need to manually Enter the `Cargo.lock`. Because of its existence, we don't need to manually
keep track of the exact revisions: Cargo will do it for us. When we have a keep track of the exact revisions: Cargo will do it for us. When we have a

2
src/doc/pkgid-spec.md
View File

@ -38,7 +38,7 @@ registry at `crates.io`
## Brevity of Specifications ## Brevity of Specifications
The goal of this is to enable both succinct and exhausitive syntaxes for The goal of this is to enable both succinct and exhaustive syntaxes for
referring to packages in a dependency graph. Ambiguous references may refer to referring to packages in a dependency graph. Ambiguous references may refer to
one or more packages. Most commands generate an error if more than one package one or more packages. Most commands generate an error if more than one package
could be referred to with the same specification. could be referred to with the same specification.