From fa87851488cf29de24d4b0e2aff4dbc249408800 Mon Sep 17 00:00:00 2001
From: Dirk Dougherty
Date: Thu, 1 Oct 2015 11:31:45 -0700
Subject: [PATCH] Doc change: edits to assist docs.
Change-Id: I5b2188c74b77606f8740ea5ebd198dceb74adda0
---
docs/html/training/articles/assistant.jd | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/html/training/articles/assistant.jd b/docs/html/training/articles/assistant.jd
index 417d97c22fb4b..e12b7c4751780 100644
--- a/docs/html/training/articles/assistant.jd
+++ b/docs/html/training/articles/assistant.jd
@@ -210,7 +210,7 @@ public void onProvideAssistContent(AssistContent assistContent)
android.app.Activity#onProvideAssistContent(android.app.assist.AssistContent)}
callbacks are implemented, the system will still proceed and pass the
information collected automatically to the assistant unless the current
- window is flagged as secure.
+ window is flagged as secure.
As shown in Figure 3, the system uses the default implementations of {@link
android.view.View#onProvideStructure(android.view.ViewStructure)} and {@link
android.view.View#onProvideVirtualStructure(android.view.ViewStructure)} to
@@ -234,7 +234,7 @@ public void onProvideAssistContent(AssistContent assistContent)
Accessible”.
-
+Excluding views from the assitant
An activity can exclude the current view from the assistant. This is accomplished
@@ -266,7 +266,7 @@ public void onProvideAssistContent(AssistContent assistContent)
current activity. The assistant can be summoned by the user at any time.
Therefore, apps should not create permanent {@link
android.Manifest.permission#SYSTEM_ALERT_WINDOW system alert}
- windows interfering with the overlay window s shown in Figure 4.
+ windows interfering with the overlay window shown in Figure 4.