am dd6977db: am 4a4603f6: am 700b54ab: am c9c15793: am 8b9d55e4: docs: Removed extraneous "system components" info

* commit 'dd6977db55cab810e484f5e49acba12a6d045d07':
  docs: Removed extraneous "system components" info

docs/html/preview/features/runtime-permissions.jd

@@ -35,12 +35,23 @@ page.image=images/permissions_check.png
 <!--
   <h2>See also</h2>
   <ol>
-    <li></li>
+    <li>
+    </li>
   </ol>
 -->
+
   </div> <!-- qv -->
 </div> <!-- qv-wrapper -->
 
+<!-- video box -->
+<a class="notice-developers-video"
+    href="https://www.youtube.com/watch?v=f17qe9vZ8RM">
+<div>
+    <h3>Video</h3>
+    <p>Google I/O 2015—Android M Permissions: Best Practices for
+      Developers</p>
+</div>
+</a>
 
 <p>
   The M Developer Preview introduces a new app permissions model which
@@ -204,12 +215,7 @@ page.image=images/permissions_check.png
 
 <ul>
   <li>System components automatically receive all
-  the permissions listed in their manifests. However, the user can still revoke
+  the permissions listed in their manifests.
-  permissions at any time by going to the system's <strong>Settings</strong>
-  app and choosing <strong>Apps &gt;</strong> <i>app_name</i> <strong>&gt;
-  Permissions</strong>. Because users can revoke these permissions at will,
-  the app should continue to check for permissions at run
-  time and request them if necessary.
   </li>
 
   <li>If the app requests permissions in the manifest that fall under {@link