@@ -804,7 +804,7 @@ confusing numbers that correspond to different units.
804804We've already seen several function definitions. Like all other static
805805declarations, such as ` type ` , functions can be declared both at the
806806top level and inside other functions (or in modules, which we'll come
807- back to [ later] ( #modules -and-crates  ) ). The ` fn `  keyword introduces a
807+ back to [ later] ( #crates -and-the-module-system  ) ). The ` fn `  keyword introduces a
808808function. A function has an argument list, which is a parenthesized
809809list of ` expr: type `  pairs separated by commas. An arrow ` -> ` 
810810separates the argument list and the function's return type.
@@ -2711,10 +2711,10 @@ extend with the `-L` switch).
27112711However, Rust also ships with rustpkg, a package manager that is able to automatically download and build
27122712libraries if you use it for building your crate. How it works is explained [ here] [ rustpkg ] ,
27132713but for this tutorial it's only important to know that you can optionally annotate an
2714- ` extern mod `  statement with an  package id that rustpkg can use to identify it:
2714+ ` extern mod `  statement with a  package id that rustpkg can use to identify it:
27152715
27162716~~~  {.ignore} 
2717- extern mod rust = "github.com/mozilla/rust"; // pretend Rust is an  simple library 
2717+ extern mod rust = "github.com/mozilla/rust"; // pretend Rust is a  simple library 
27182718~~~ 
27192719
27202720[ rustpkg ] : rustpkg.html 
@@ -2730,7 +2730,7 @@ the link name and the version. It also hashes the filename and the symbols in a
27302730based on the link metadata, allowing you to use two different versions of the same library in a crate
27312731without conflict.
27322732
2733- Therefor , if you plan to compile your crate as a library, you should annotate it with that information:
2733+ Therefore , if you plan to compile your crate as a library, you should annotate it with that information:
27342734
27352735~~~~ 
27362736// lib.rs 
@@ -2746,8 +2746,8 @@ Therefor, if you plan to compile your crate as a library, you should annotate it
27462746You can also in turn require in a ` extern mod `  statement that certain link metadata items match some criteria.
27472747For that, Rust currently parses a comma-separated list of name/value pairs that appear after
27482748it, and ensures that they match the attributes provided in the ` link `  attribute of a crate file.
2749- This enables you to, eg , pick a a  crate based on it's  version number, or to  link an  library under an 
2750- different name. For example, this  two mod statements would both accept and select the crate define above:
2749+ This enables you to, e.g. , pick a crate based on its  version number, or link a  library under a 
2750+ different name. For example, these  two ` mod `  statements would both accept and select the crate define above:
27512751
27522752~~~~  {.xfail-test} 
27532753extern mod farm(vers = "2.5"); 
@@ -2836,14 +2836,14 @@ This allows you to use common types and functions like `Option<T>` or `println`
28362836without needing to import them. And if you need something from ` std `  that's not in the prelude,
28372837you just have to import it with an ` use `  statement.
28382838
2839- For example, it re-exports ` println `  which is defined in ` std::io::println ` :
2839+ For example, it re-exports ` println `  which is defined in ` std::io::stdio:: println ` :
28402840
28412841~~~ 
28422842use puts = std::io::stdio::println; 
28432843
28442844fn main() { 
28452845    println("println is imported per default."); 
2846-     puts("Doesn't hinder you from importing it under an  different name yourself."); 
2846+     puts("Doesn't hinder you from importing it under a  different name yourself."); 
28472847    ::std::io::stdio::println("Or from not using the automatic import."); 
28482848} 
28492849~~~ 
0 commit comments