Switch to https for most links
Update obsolete links (groups, android doc on code.google.com)
Update instructions related to groups
Change-Id: I29a50cb5f026f0e1e00f2d2aadcfa2a138a96a03
diff --git a/src/compatibility/cts-intro.md b/src/compatibility/cts-intro.md
index 0f62b84..842a583 100644
--- a/src/compatibility/cts-intro.md
+++ b/src/compatibility/cts-intro.md
@@ -87,10 +87,10 @@
Area | Description
-----|-------------
Signature tests | For each Android release, there are XML files describing the signatures of all public APIs contained in the release. The CTS contains a utility to check those API signatures against the APIs available on the device. The results from signature checking are recorded in the test result XML file.
-Platform API Tests | Test the platform (core libraries and Android Application Framework) APIs as documented in the SDK [Class Index](http://code.google.com/android/reference/classes.html) to ensure API correctness, including correct class, attribute and method signatures, correct method behavior, and negative tests to ensure expected behavior for incorrect parameter handling.
+Platform API Tests | Test the platform (core libraries and Android Application Framework) APIs as documented in the SDK [Class Index](https://developer.android.com/reference/classes.html) to ensure API correctness, including correct class, attribute and method signatures, correct method behavior, and negative tests to ensure expected behavior for incorrect parameter handling.
Dalvik VM Tests | The tests focus on testing the Dalvik VM
-Platform Data Model | The CTS tests the core platform data model as exposed to application developers through content providers, as documented in the SDK [android.provider](http://code.google.com/android/reference/android/provider/package-summary.html) package: contacts, browser, settings, etc.
-Platform Intents | The CTS tests the core platform intents, as documented in the SDK [Available Intents](http://code.google.com/android/reference/available-intents.html).
-Platform Permissions | The CTS tests the core platform permissions, as documented in the SDK [Available Permissions](http://code.google.com/android/reference/android/Manifest.permission.html).
-Platform Resources | The CTS tests for correct handling of the core platform resource types, as documented in the SDK [Available Resource Types](http://code.google.com/android/reference/available-resources.html). This includes tests for: simple values, drawables, nine-patch, animations, layouts, styles and themes, and loading alternate resources.
+Platform Data Model | The CTS tests the core platform data model as exposed to application developers through content providers, as documented in the SDK [android.provider](https://developer.android.com/reference/android/provider/package-summary.html) package: contacts, browser, settings, etc.
+Platform Intents | The CTS tests the core platform intents, as documented in the SDK [Available Intents](https://developer.android.com/guide/appendix/g-app-intents.html).
+Platform Permissions | The CTS tests the core platform permissions, as documented in the SDK [Available Permissions](https://developer.android.com/reference/android/Manifest.permission.html).
+Platform Resources | The CTS tests for correct handling of the core platform resource types, as documented in the SDK [Available Resource Types](https://developer.android.com/guide/topics/resources/available-resources.html). This includes tests for: simple values, drawables, nine-patch, animations, layouts, styles and themes, and loading alternate resources.