From 3f2f53057fb854fbcf0b113dc48201f67adf0269 Mon Sep 17 00:00:00 2001 From: "L. David Baron" Date: Thu, 23 May 2019 09:56:04 +0000 Subject: [PATCH] Fix a few typos and reword one bit that's unclear. --- css-nav-1/explainer.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/css-nav-1/explainer.md b/css-nav-1/explainer.md index a477597fb65..98f3f8cd109 100644 --- a/css-nav-1/explainer.md +++ b/css-nav-1/explainer.md @@ -106,7 +106,7 @@ to extend how spatial navigation work. The spec supposes that User Agents decide to activate spatial navigation. On devices which do not have any pointing input device, and especially on devices such as TVs which also lack a Tab key to control -sequential focus navigation, +sequential focus navigation, User Agents should make spatial navigation active. We deliberately do not define which keys or key combination are meant to trigger the spatial navigation, @@ -340,8 +340,8 @@ There are several approaches. * related github issue: https://github.com/WICG/spatial-navigation/issues/41 -2. Using the spatial navigation API -If the spatial navigation is implemented, one of the API can be the criteria for the enablility of the spatial navigation +2. Using the spatial navigation API: +If the spatial navigation is implemented, one of the APIs can be used to detect whether spatial navigation is enabled. For example, ``` @@ -386,7 +386,7 @@ For example, the spatial navigation feature is allowed when the feature policy i | Origin | Policy | |-|-| -| Default | sptialnavigation 'self' | +| Default | spatialnavigation 'self' | | example.com | `Feature-Policy: spatialnavigation https://game.com` | | game.com | `` |