[llvm] f7ca0c7 - [docs] Fix duplicate explicit target name: developer policy

[Jim Lin via llvm-commits]

Author: Jim Lin
Date: 2020-01-08T10:44:44+08:00
New Revision: f7ca0c761979f0a06894571245a913cd8e2dbfce

URL: https://github.com/llvm/llvm-project/commit/f7ca0c761979f0a06894571245a913cd8e2dbfce
DIFF: https://github.com/llvm/llvm-project/commit/f7ca0c761979f0a06894571245a913cd8e2dbfce.diff

LOG: [docs] Fix duplicate explicit target name: developer policy

Added: 
    

Modified: 
    llvm/docs/GettingStarted.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/GettingStarted.rst b/llvm/docs/GettingStarted.rst
index 6dfca656d435..35c021ee3209 100644
--- a/llvm/docs/GettingStarted.rst
+++ b/llvm/docs/GettingStarted.rst
@@ -494,8 +494,8 @@ Once a patch is reviewed, you should rebase it, re-test locally, and commit the
 changes to LLVM's master branch. This is done using `git push` if you have the
 required access rights. See `committing a change
 <Phabricator.html#committing-a-change>`_ for Phabricator based commits or
-`Developer Policy <DeveloperPolicy.html#obtaining-commit-access>`_ for commit
-access.
+`obtaining commit access <DeveloperPolicy.html#obtaining-commit-access>`_
+for commit access.
 
 LLVM currently has a linear-history policy, which means that merge commits are
 not allowed. The `llvm-project` repo on github is configured to reject pushes