Update RELEASES.md

RELEASES.md

@@ -10,12 +10,6 @@ The semantics are: MAJOR.MINOR.PATCH (example 1.1.5)
 
 We will update our code distributions to use the latest PATCH semantic version number in order to make sure our customers and partners get the latest bug fixes. Downstream partner needs to pull the latest PATCH version. Most partners should try lock on the latest MINOR version number in their builds and accept any updates in the PATCH number.
 
-Examples:
-Using Cocapods, the following in the podfile will take the latest ADALiOS build that is > 1.1 but not 1.2.
-```
-pod 'ADALiOS', '~> 1.1'
-```
-
 Using NuGet, this ensures all 1.1.0 to 1.1.x updates are included when building your code, but not 1.2. 
 
 ```
@@ -43,4 +37,4 @@ Example: We release ADALiOS 2.0 in the future which supports unified Auth for AA
 Microsoft Identity SDKs major versions will maintain backwards compatibility with Azure Active Directory web services through the support period. This means that the API surface area defined in a MAJOR version will continue to work for 2 years after release.
 
 We will respond to bugs quickly from our partners and customers submitted through GitHub and through our private alias ([email protected]) for security issues and update the PATCH version number. We will also submit a change summary for each PATCH number.
-Occasionally, there will be security bugs or breaking bugs from our partners that will require an immediate fix and a publish of an update to all partners and customers. When this occurs, we will do an emergency roll up to a PATCH version number and update all our distribution methods to the latest.
+Occasionally, there will be security bugs or breaking bugs from our partners that will require an immediate fix and a publish of an update to all partners and customers. When this occurs, we will do an emergency roll up to a PATCH version number and update all our distribution methods to the latest.