From 264ece1f725e4b35d3c7e5a9bfe8230b352c8ea3 Mon Sep 17 00:00:00 2001 From: Justas Brazauskas Date: Tue, 15 Dec 2015 18:13:25 +0200 Subject: [PATCH] Fix typos in ./docs --- docs/Accessibility.md | 2 +- docs/Tutorial.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Accessibility.md b/docs/Accessibility.md index 10ac5884a..b968642c8 100644 --- a/docs/Accessibility.md +++ b/docs/Accessibility.md @@ -81,7 +81,7 @@ Assign this property to a custom function which will be called when someone perf #### accessibilityComponentType (Android) -In some cases, we also want to alert the end user of the type of selected component (ie, that it is a “button”). If we were using native buttons, this would work automatically. Since we are using javascript, we need to provide a bit more context for TalkBack. To do so, you must specify the ‘accessibilityComponentType’ property for any UI component. For instances, we support ‘button’, ‘radiobutton_checked’ and ‘radiobutton_unchecked’ and so on. +In some cases, we also want to alert the end user of the type of selected component (i.e., that it is a “button”). If we were using native buttons, this would work automatically. Since we are using javascript, we need to provide a bit more context for TalkBack. To do so, you must specify the ‘accessibilityComponentType’ property for any UI component. For instances, we support ‘button’, ‘radiobutton_checked’ and ‘radiobutton_unchecked’ and so on. ```javascript