fixing build script docs mistakes

diff --git a/src/doc/build-script.md b/src/doc/build-script.md
index f5fe8e283fb30404e5beacf83064cb6034a4582c..9844ee235d5b8e591dfc261616d21ee85b66ff49 100644 (file)
--- a/src/doc/build-script.md
+++ b/src/doc/build-script.md
@@ -81,7 +81,7 @@ crate is built:
   out in crates.io crates are not emitted by default.
 
 Any other element is a user-defined metadata that will be passed to
-dependencies. More information about this can be found in the [`links`][links]
+dependents. More information about this can be found in the [`links`][links]
 section.
 
 [links]: #the-links-manifest-key
@@ -252,9 +252,7 @@ This is where the real magic happens. The library is using the rustc-defined
 the generated file (`hello.rs`) into the crate’s compilation.
 
 Using the structure shown here, crates can include any number of generated files
-from the build script itself. We’ve also seen a brief example of how a build
-script can use a crate as a dependency purely for the build process and not for
-the crate itself at runtime.
+from the build script itself.
 
 # Case study: Building some native code
 
@@ -400,6 +398,9 @@ And there we go! This should complete our example of building some C code from a
 Cargo package using the build script itself. This also shows why using a build
 dependency can be crucial in many situations and even much more concise!
 
+We’ve also seen a brief example of how a build script can use a crate as a
+dependency purely for the build process and not for the crate itself at runtime.
+
 # Case study: Linking to system libraries
 
 The final case study here will be investigating how a Cargo library links to a