match.md in fastlane-2.62.0.beta.20171014010003

- old
+ new
@@ -248,24 +248,24 @@
 
 _match_ can even use the same one Git repository for all bundle identifiers.
 
 ### Setup Xcode project
 
-[Docs on how to set up your Xcode project](https://docs.fastlane.tools/codesigning/XcodeProject/)
+[Docs on how to set up your Xcode project](/codesigning/xcode-project/)
 
 #### To build from the command line using [fastlane](https://fastlane.tools)
 
 _match_ automatically pre-fills environment variables with the UUIDs of the correct provisioning profiles, ready to be used in your Xcode project.
 
-More information about how to setup your Xcode project can be found [here](https://docs.fastlane.tools/codesigning/XcodeProject/)
+More information about how to setup your Xcode project can be found [here](/codesigning/xcode-project/)
 
 #### To build from Xcode manually
 
 This is useful when installing your application on your device using the Development profile.
 
 You can statically select the right provisioning profile in your Xcode project (the name will be `match Development tools.fastlane.app`).
 
-[Docs on how to set up your Xcode project](/codesigning/xcode-project/.md)
+[Docs on how to set up your Xcode project](/codesigning/xcode-project/)
 
 ### Continuous Integration
 
 #### Repo access
 There is one tricky part of setting up a CI system to work with _match_, which is enabling the CI to access the repo. Usually you'd just add your CI's public ssh key as a deploy key to your _match_ repo, but since your CI will already likely be using its public ssh key to access the codebase repo, [you won't be able to do that](https://help.github.com/articles/error-key-already-in-use/).