Small edit/tweaks in README.md

README.md

@@ -10,7 +10,7 @@ among the [maintainers].
 The "RFC" (request for comments) process is intended to provide a consistent
 and predictable path for new features and projects.
 
-[Active RFC List](https://github.com/rubygems/rfcs/pulls)
+[Active RFC List](https://github.com/bundler/rfcs/pulls)
 
 ## When you need to follow this process
 
@@ -46,7 +46,7 @@ RFC pull request with the specific implementation design.
 
 ## What the process is
 
-In short, any major feature nedes an RFC that has been merged into this RFC
+In short, any major feature needs an RFC that has been merged into this RFC
 repo as a markdown file. At that point the RFC is 'active' and may be
 implemented with the goal of eventual inclusion into Bundler and/or RubyGems.
 
@@ -61,7 +61,11 @@ implemented with the goal of eventual inclusion into Bundler and/or RubyGems.
   response.
 * Build consensus and integrate feedback. RFCs that have broad support are much
   more likely to make progress than those that don't receive any comments.
-* RFCs rarely go through this process unchanged, especially as alternatives and drawbacks are shown. You can make edits, big and small, to the RFC to clarify or change the design, but make changes as new commits to the PR, and leave a comment on the PR explaining your changes. Specifically, do not squash or rebase commits after they are visible on the PR.
+* RFCs rarely go through this process unchanged, especially as alternatives and 
+  drawbacks are shown. You can make edits, big and small, to the RFC to clarify 
+  or change the design, but make changes as new commits to the PR, and leave a 
+  comment on the PR explaining your changes. Specifically, do not squash or 
+  rebase commits after they are visible on the PR.
 * RFCs that are candidates for inclusion will enter a "final comment period"
   lasting 7 days. The beginning of this period will be signaled with a comment
   and tag on the RFC's pull request. At that point, the [Bundler Twitter