Updating CONTRIBUTING.md

AuthorizeNet · gnongsie · Oct 15, 2018 · Oct 10, 2017 · Oct 10, 2017 · Oct 10, 2017
commit f49c454ea343dea98e9ad71e3ffd41e56531afa4
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -5,5 +5,5 @@ Before you submit a pull request, we ask that you consider the following:
 - Submit an issue to state the problem your pull request solves or the funtionality that it adds. We can then advise on the feasability of the pull request, and let you know if there are other possible solutions.
 - Part of the SDK is auto-generated based on the XML schema. Due to this auto-generation, we cannot merge contributions for request or response classes. You are welcome to open an issue to report problems or suggest improvements. Auto-generated classes include all files inside [contract/v1](https://github.com/AuthorizeNet/sdk-java/tree/master/src/main/java/net/authorize/api/contract/v1)  and [controller](https://github.com/AuthorizeNet/sdk-java/tree/master/src/main/java/net/authorize/api/controller) folders, except [controller/base](https://github.com/AuthorizeNet/sdk-java/tree/master/src/main/java/net/authorize/api/controller/base).
 - Files marked as deprecated are no longer supported. Issues and pull requests for changes to these deprecated files will be closed.
-- Recent changes will be in future branch. Check the code in *future* branch first to see if a fix has already been merged, before suggesting changes to a file.
-- **Always create pull request to the future branch.** The pull request will be merged to future, and later pushed to master as part of the next release. 
+- Recent changes will be in the [future branch](https://github.com/AuthorizeNet/sdk-java/tree/future). Before submitting an issue or pull request, check the future branch first to see if a fix has already been merged.
+- **Always use the future branch for pull requests.** We will first merge pull requests to the future branch, before pushing to the master branch for the next release.