From 53fcc756d06ed382e7b02b266631f7848d1b9c4f Mon Sep 17 00:00:00 2001
From: Felipe Leme <felipeal@google.com>
Date: Wed, 17 Feb 2016 14:45:52 -0800
Subject: [PATCH] Fixed typo on Storage Access Framework.

BUG: 26742218
Change-Id: I9b695ebe2176f186fc63b20f624e40dd9e257bc3
---
 core/java/android/os/storage/StorageVolume.java | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/core/java/android/os/storage/StorageVolume.java b/core/java/android/os/storage/StorageVolume.java
index f838aec019308..d860c7d8ad2e2 100644
--- a/core/java/android/os/storage/StorageVolume.java
+++ b/core/java/android/os/storage/StorageVolume.java
@@ -55,9 +55,10 @@ import java.io.File;
  * <li>To get access to standard directories (like the {@link Environment#DIRECTORY_PICTURES}), they
  * can use the {@link #createAccessIntent(String)}. This is the recommend way, since it provides a
  * simpler API and narrows the access to the given directory (and its descendants).
- * <li>To get access to any directory (and its descendants), they can use the Storage Area Framework
- * APIs (such as {@link Intent#ACTION_OPEN_DOCUMENT} and {@link Intent#ACTION_OPEN_DOCUMENT_TREE},
- * although these APIs do not guarantee the user will select this specific volume.
+ * <li>To get access to any directory (and its descendants), they can use the Storage Acess
+ * Framework APIs (such as {@link Intent#ACTION_OPEN_DOCUMENT} and
+ * {@link Intent#ACTION_OPEN_DOCUMENT_TREE}, although these APIs do not guarantee the user will
+ * select this specific volume.
  * <li>To get read and write access to the primary storage volume, applications can declare the
  * {@link android.Manifest.permission#READ_EXTERNAL_STORAGE} and
  * {@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE} permissions respectively, with the