Change to  suffix
@@ -41,24 +41,24 @@ Twilio frequently rolls out new features in public and private beta periods.
Twilio strives to ship early and often and bake customer feedback back into our
products. To support that mission, the `twilio-python` helper library has an
`Edge` version based off the `alpha` branch. This version is identified with an
-`alpha` metadata tag on the version number.
+`a` metadata tag on the version number.
The way the `Edge` artifact is created is by playing the `Edge` features on top
of our stable artifact. The `Edge` artifact will always have the same version
-number as the stable artifact it was created from, but with an `alpha` suffix.
+number as the stable artifact it was created from, but with an `a` suffix.
-For example, `6.0.0-alpha-1` is the `6.0.0` branch with `Edge` features included.
+For example, `6.0.0a1` is the `6.0.0` branch with `Edge` features included.
If there is a change to one of the `Edge` features we may regenerate the `Edge`
-artifact and release a new `6.0.0-alpha-2`, new `Edge` artifacts simply increment
-the number after the `alpha` suffix. All `Edge` features are considered
+artifact and release a new `6.0.0a2`, new `Edge` artifacts simply increment
+the number after the `a` suffix. All `Edge` features are considered
unstable and a backwards incompatible change in an `Edge` feature will not cause
-any version change so you should take care when upgrading from one `alpha`
+any version change so you should take care when upgrading from one `a`
version to another.
Once an `Edge` feature has matured it will be considered `Mainline` and included
in the stable artifact, with a `MAJOR` or `MINOR` version bump.
To use an `Edge` artifact in your PYTHON project you will have to make sure that
-you pin the artifact with `alpha` stability in your `setup.py` or `requirements.txt`.
+you pin the artifact with `a` stability in your `setup.py` or `requirements.txt`.
[semver]: http://semver.org/
