7 files changed, 50 insertions, 10 deletions
diff --git a/en/devices/tech/config/filesystem.html b/en/devices/tech/config/filesystem.html
index 10b7f0b4..73633943 100644
--- a/en/devices/tech/config/filesystem.html
+++ b/en/devices/tech/config/filesystem.html
@@ -244,7 +244,8 @@ the autogenerated header file by adding to your module's <code>Android.mk</code>
 and including the empty faux library. For example, in <code>Android.mk</code>,
 add the following:</p>
 
-<pre class="prettyprint"> LOCAL_STATIC_LIBRARIES := liboemaids</pre>
+<pre class="prettyprint">LOCAL_HEADER_LIBRARIES := oemaids_headers</pre>
+
 <p>In your C code, <code>#include "generated_oem_aid.h"</code> and start using
 the declared identifiers. For example, in <code>my_file.c</code>, add the
 following: </p>
diff --git a/en/devices/tech/config/namespaces_libraries.html b/en/devices/tech/config/namespaces_libraries.html
index b91cbe23..1e94bf1b 100644
--- a/en/devices/tech/config/namespaces_libraries.html
+++ b/en/devices/tech/config/namespaces_libraries.html
@@ -61,6 +61,26 @@ additional native libraries accessible to apps by putting them under the
 <code>/vendor/etc/public.libraries.txt</code>
 </p>
 
+<p>
+Starting from Android 8.0, vendor public libraries have the following additional
+restrictions and required setups:
+</p>
+
+<ol>
+  <li>The native library in vendor must be properly labeled so it can be
+    accessible to apps. If access is required by any apps (including third
+    party apps), the library must be labeled as <code>same_process_hal_file</code>
+    in a vendor-specific <code>file_contexts</code> file as follows:
+    <pre class="devsite-click-to-copy">/vendor/lib(64)?/libnative.so u:object_r:same_process_hal_file:s0</pre>
+    where <code>libnative.so</code> is the name of the native library.
+  </li>
+  <li>The library, either directly or transitively via its dependencies, must not
+    depend on system libraries other than VNDK-SP and LLNDK libraries. The list of
+    VNDK-SP and LLNDK libraries can be found at
+    <code>development/vndk/tools/definition/tool/datasets/eligible-list-&lt;version&gt;-release.csv</code>.
+  </li>
+</ol>
+
 <h2 id="updating-app-non-public">Updating apps to not use non-public native libraries</h2>
 
 <p>
diff --git a/en/devices/tech/config/perms-whitelist.html b/en/devices/tech/config/perms-whitelist.html
index c3de0de0..918f89eb 100644
--- a/en/devices/tech/config/perms-whitelist.html
+++ b/en/devices/tech/config/perms-whitelist.html
@@ -135,7 +135,7 @@
   transitional log-mode:
 </p>
 
-<pre class="devsite-click-to-copy">ro.control_privapp_permission=log</pre>
+<pre class="devsite-click-to-copy">ro.control_privapp_permissions=log</pre>
 
 <p>
   Violations are reported in the log file, but permissions are still granted.
@@ -158,11 +158,11 @@ PackageManager: Privileged permission {PERMISSION_NAME} for package {PACKAGE_NAM
 
 <p>
   After whitelists are in place, enable runtime enforcement by setting the build
-  property <code>ro.control_privapp_permission=enforce</code>.
+  property <code>ro.control_privapp_permissions=enforce</code>.
 </p>
 
 <aside class="note"><strong>Note:</strong> The
-  <code>ro.control_privapp_permission</code> property state must adhere to
+  <code>ro.control_privapp_permissions</code> property state must adhere to
   <a href="/compatibility/android-cdd#9_1_permissions">CDD section 9.1
   requirements</a>.</aside>
 
diff --git a/en/devices/tech/config/uicc.html b/en/devices/tech/config/uicc.html
index 1fa6952c..96c1d360 100644
--- a/en/devices/tech/config/uicc.html
+++ b/en/devices/tech/config/uicc.html
@@ -29,7 +29,7 @@ Android platform loads certificates stored on a UICC and grants permission to
 apps signed by these certificates to make calls to a handful of special APIs.
 </p>
 <p>Android 7.0 extends this feature to support other storage sources, such as
-Access File Rule (ARF), for UICC carrier privilege rules, dramatically
+Access Rule File (ARF), for UICC carrier privilege rules, dramatically
 increasing the number of carriers that can use the APIs. For an API reference,
 see <a href="#carrierconfigmanager">CarrierConfigManager</a>; for instructions,
 see <a href="/devices/tech/config/carrier.html">Carrier
diff --git a/en/devices/tech/ota/ab/index.html b/en/devices/tech/ota/ab/index.html
index 48a9fea5..c2a9c447 100644
--- a/en/devices/tech/ota/ab/index.html
+++ b/en/devices/tech/ota/ab/index.html
@@ -31,6 +31,9 @@
       updates successfully.
     </p>
 
+    <p>For more information about A/B system updates and how they work, see
+      <a href="#slots">Partition selection (slots)</a>.
+
     <p>A/B system updates provide the following benefits:</p>
 
     <ul>
diff --git a/en/devices/tech/ota/index.html b/en/devices/tech/ota/index.html
index 1565e3b2..7b2f0dd0 100644
--- a/en/devices/tech/ota/index.html
+++ b/en/devices/tech/ota/index.html
@@ -35,7 +35,7 @@
       applications installed by the user from Google Play.
     </p>
 
-    <h2 id="ab_updates">A/B updates</h2>
+    <h2 id="ab_updates">A/B (seamless) system updates</h2>
 
       <p>
         Modern A/B devices have two copies of each partition, A and B. Devices
@@ -50,7 +50,7 @@
         </a>.
       </p>
 
-    <h2 id="nonab_updates">Non-A/B updates</h2>
+    <h2 id="nonab_updates">Non-A/B system updates</h2>
 
       <p>
         Older devices have a special recovery partition containing the software
diff --git a/en/devices/tech/perf/boot-times.html b/en/devices/tech/perf/boot-times.html
index a7588301..fb6ad441 100644
--- a/en/devices/tech/perf/boot-times.html
+++ b/en/devices/tech/perf/boot-times.html
@@ -255,17 +255,27 @@ us uncover many meaningful bugs in some Android device drivers).
 Many processes launch during boot, but only components in critical path
 (bootloader > kernel > init > file system mount > zygote > system server)
 directly affect boot time. Profile <strong>initcall</strong> during kernel
-booting to identify peripheral/components that are not critical to the
-start init process, then delay those peripherals/components until later
-in the boot process.
+booting to identify peripheral/components that are slow and not critical
+to start init process, then delay those peripherals/components until later
+in the boot process by moving into loadable kernel modules. Moving to
+asynchronous device/driver probe can also help to parallel slow components
+in kernel > init critical path.
 </p>
 
 <pre
 class="prettyprint">
 BoardConfig-common.mk:
     BOARD_KERNEL_CMDLINE += initcall_debug ignore_loglevel
+
+driver:
+    .probe_type = PROBE_PREFER_ASYNCHRONOUS,
 </pre>
 
+<p class="note">
+<strong>Note:</strong> Driver dependencies must be resolved carefully by adding
+<code>EPROBEDEFER</code> support.
+</p>
+
 <h2 id="optimizing-i-o-efficiency">Optimizing I/O efficiency</h2>
 
 <p>
@@ -422,6 +432,12 @@ early stage init should be deferred to boot completed.</li></ul>
 </li>
 </ul>
 
+<p class="note">
+<strong>Note:</strong> Property service is part of init process, so calling
+<code>setproperty</code> during boot can lead a long delay if init is busy in
+builtin commands.
+</p>
+
 <h3 id="using-scheduler-tuning">Using scheduler tuning</h3>
 
 <p>