Update RFC Process document with procedure one follows with new dir layout.

Author: pnkfelix

text/0002-rfc-process.md

@@ -61,7 +61,7 @@ is 'active' and may be implemented with the goal of eventual inclusion
 into Rust.
 
 * Fork the RFC repo https://github.com/rust-lang/rfcs
-* Copy `0000-template.md` to `active/0000-my-feature.md` (where
+* Copy `0000-template.md` to `text/0000-my-feature.md` (where
 'my-feature' is descriptive. don't assign an RFC number yet).
 * Fill in the RFC
 * Submit a pull request. The pull request is the time to get review of
@@ -71,16 +71,19 @@ are much more likely to make progress than those that don't receive any
 comments.
 
 Eventually, somebody on the [core team] will either accept the RFC by
-merging the pull request and assigning the RFC a number, at which point
-the RFC is 'active', or reject it by closing the pull request.
+merging the pull request, at which point the RFC is 'active', or
+reject it by closing the pull request.
 
 Whomever merges the RFC should do the following:
 
-* Assign a sequential id.
-* Add the file in the active directory.
-* Create a corresponding issue on Rust.
-* Fill in the remaining metadata in the RFC header, including the original
-  PR # and Rust issue #.
+* Assign an id, using the PR number of the RFC pull request. (If the RFC
+  has multiple pull requests associated with it, choose one PR number,
+  preferably the minimal one.)
+* Add the file in the `text/` directory.
+* Create a corresponding issue on [Rust repo](https://github.com/rust-lang/rust)
+* Fill in the remaining metadata in the RFC header, including links for
+  the original pull request(s) and the newly created Rust issue.
+* Add an entry in the [Active RFC List] of the root `README.md`.
 * Commit everything.
 
 Once an RFC becomes active then authors may implement it and submit the
@@ -91,9 +94,11 @@ have agreed to the feature and are amenable to merging it.
 
 Modifications to active RFC's can be done in followup PR's. An RFC that
 makes it through the entire process to implementation is considered
-'complete' and is moved to the 'complete' folder; an RFC that fails
+'complete' and is removed from the [Active RFC List]; an RFC that fails
 after becoming active is 'inactive' and moves to the 'inactive' folder.
 
+[Active RFC List]: ../README.md#active-rfc-list
+
 # Alternatives
 
 Retain the current informal RFC process. The newly proposed RFC process is