Rephrase the backport sectio

Rephrase the backport sectoin, since development branch is not a legacy branch
gilles-peskine-arm · Sep 3, 2017 · 0a47d12 · 0a47d12
1 parent ea24d75
commit 0a47d12
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -34,12 +34,11 @@ mbed TLS maintains some legacy branches, which are released as LTS versions. mbe
 1. Bug fixes should be backported to the legacy branches containing these bugs.
 1. Changes in the API do not require backporting. If a bug fix introduced a new API, such as new error codes, the bug fix should be implemented differently in the legacy branch.
 
-It would be highly appreciated if a contribution would be backported to a legacy branch as well.  
+It would be highly appreciated if a contribution would be backported to a legacy branch in addition to the [development branch](https://github.com/ARMmbed/mbedtls/tree/development).
 At the moment, the legacy branches are:
 
 1. [mbedtls-1.3](https://github.com/ARMmbed/mbedtls/tree/mbedtls-1.3)
 1. [mbedtls-2.1](https://github.com/ARMmbed/mbedtls/tree/mbedtls-2.1)
-1. [development](https://github.com/ARMmbed/mbedtls/tree/development)
 
 Tests
 -----