[Docs] Fix some nits discovered while converting to Markdown

docs/becoming_v8_committer.md

Index: docs/becoming_v8_committer.md
diff --git a/docs/becoming_v8_committer.md b/docs/becoming_v8_committer.md
index 16e8491b06f1f95f0021d8aa73295b84c01c35a2..0a927b3ca9f72d93a162ec002e054cf51e4a4bc4 100644
--- a/docs/becoming_v8_committer.md
+++ b/docs/becoming_v8_committer.md
@@ -1,6 +1,8 @@
+# Becoming a V8 committer
+
 ## What is a committer?
 
-Technically, a committer is someone who has write access to the V8 SVN repository. A committer can submit his or her own patches or patches from others.
+Technically, a committer is someone who has write access to the V8 Git repository. A committer can submit his or her own patches or patches from others.
 
 This privilege is granted with some expectation of responsibility: committers are people who care about the V8 project and want to help meet its goals. A committer is not just someone who can make changes, but someone who has demonstrated his or her ability to collaborate with the team, get the most knowledgeable people to review code, contribute high-quality code, and follow through to fix issues (in code or tests).
 
@@ -35,4 +37,4 @@ You don't really need to do much to maintain committer status: just keep being a
 
 In the unhappy event that a committer continues to disregard good citizenship (or actively disrupts the project), we may need to revoke that person's status. The process is the same as for nominating a new committer: someone suggests the revocation with a good reason, two people second the motion, and a vote may be called if consensus cannot be reached. I hope that's simple enough, and that we never have to test it in practice.
 
-(Source: inspired by http://dev.chromium.org/getting-involved/become-a-committer )
+(Source: inspired by http://dev.chromium.org/getting-involved/become-a-committer )