Skip to content
Browse files
manual -> reference & formatting
'reference' sounds better than 'manual' to me here, and rust.html is
certainly wrong.

I also wrapped everything to 80 cols.
  • Loading branch information
steveklabnik committed Sep 22, 2014
1 parent 437179e commit 47682f96de1da3bb0986e44e529cc51f24549c86
Show file tree
Hide file tree
Showing 7 changed files with 4,452 additions and 4,422 deletions.
@@ -29,9 +29,9 @@ DOCS := index intro tutorial guide guide-ffi guide-macros guide-lifetimes \
guide-tasks guide-container guide-pointers guide-testing \
guide-runtime complement-bugreport \
complement-lang-faq complement-design-faq complement-project-faq rust \
rustdoc guide-unsafe guide-strings
rustdoc guide-unsafe guide-strings reference

PDF_DOCS := guide rust
PDF_DOCS := guide reference

RUSTDOC_DEPS_rust := doc/
RUSTDOC_FLAGS_rust := --html-in-header=doc/
@@ -30,7 +30,7 @@ To generate an HTML version of a doc from Markdown manually, you can do
something like:

pandoc --from=markdown --to=html5 --number-sections -o rust.html
pandoc --from=markdown --to=html5 --number-sections -o reference.html

( being the Rust Reference Manual.)
@@ -46,7 +46,7 @@ development of Rust itself is discussed.
# Specification

Rust does not have an exact specification, but an effort to describe as much of
the language in as much detail as possible is in [the manual](rust.html).
the language in as much detail as possible is in [the reference](reference.html).

# Guides

@@ -13,7 +13,7 @@ Some things that might be helpful to you though:

## Reference
* [The Rust official site](
* [The Rust reference manual]( (* [PDF](
* [The Rust reference]( (* [PDF](

## Docs
* [The standard library](

0 comments on commit 47682f9

Please sign in to comment.