If you're just reporting a bug, please see:
-http://static.rust-lang.org/doc/master/complement-bugreport.html
+http://doc.rust-lang.org/complement-bugreport.html
+
+## Submitting an issue
+
+Please submit issues here for bug reports or implementation details. For feature
+requests, language changes, or major changes to the libraries, please submit an
+issue against the [RFCs repository](https://github.com/rust-lang/rfcs).
## Pull request procedure
2. Run the full Rust test suite with the `make check` command. You're
not off the hook even if you just stick to documentation; code
- examples in the docs are tested as well!
+ examples in the docs are tested as well! Although for simple
+ wording or grammar fixes, this is probably unnecessary.
Pull requests will be treated as "review requests", and we will give
feedback we expect to see corrected on
-[style](https://github.com/mozilla/rust/wiki/Note-style-guide) and
+[style](https://github.com/rust-lang/rust/wiki/Note-style-guide) and
substance before pulling. Changes contributed via pull request should
focus on a single issue at a time, like any other. We will not accept
pull-requests that try to "sneak" unrelated changes in.
Normally, all pull requests must include regression tests (see
-[Note-testsuite](https://github.com/mozilla/rust/wiki/Note-testsuite))
+[Note-testsuite](https://github.com/rust-lang/rust/wiki/Note-testsuite))
that test your change. Occasionally, a change will be very difficult
to test for. In those cases, please include a note in your commit
message explaining why.
```
For more details, please refer to
-[Note-development-policy](https://github.com/mozilla/rust/wiki/Note-development-policy).
+[Note-development-policy](https://github.com/rust-lang/rust/wiki/Note-development-policy).