Merge pull request #390 from w3c/fix-typo

Fix typo

Author: anssiko

index.bs

@@ -356,7 +356,7 @@ The Generic Sensor API and its [=extension specifications=] are agnostic with re
 interface aspects. This specification defines an [[#request-sensor-access|integration point]] to the
 Permissions API [[PERMISSIONS]] that implementers can use for [=new information about the user's intent|
 explicit or implicit user consenting=]. In addition, implementers are encouraged to use additional
-privacy enchancing mechanisms inline with their product requirements to provide a consistent and
+privacy-enhancing mechanisms inline with their product requirements to provide a consistent and
 cohesive experience. Such mechanisms can include, for example, global and per-origin access controls,
 page info dialogs, location bar indicators, or other disclosure user interface elements.
 

index.html

@@ -1221,7 +1221,7 @@
   </style>
   <meta content="Bikeshed version df1bf04b71c9fb8a3d724e46fc13f9cf7065df60" name="generator">
   <link href="https://www.w3.org/TR/generic-sensor/" rel="canonical">
-  <meta content="dd45f8f586dd2c310eca6b5dbc24cc31bf4678e4" name="document-revision">
+  <meta content="87489306f0161b67f7db025365781946ce2de780" name="document-revision">
 <style>
     svg g.edge text {
         font-size: 8px;
@@ -1501,7 +1501,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">Generic Sensor API</h1>
-   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2019-03-11">11 March 2019</time></span></h2>
+   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2019-03-19">19 March 2019</time></span></h2>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:
@@ -1848,7 +1848,7 @@ <h2 class="heading settled" data-level="4" id="security-and-privacy"><span class
     <p>The Generic Sensor API and its <a data-link-type="dfn" href="#extension-specification" id="ref-for-extension-specification">extension specifications</a> are agnostic with respect to any user
 interface aspects. This specification defines an <a href="#request-sensor-access" id="ref-for-request-sensor-access">integration point</a> to the
 Permissions API <a data-link-type="biblio" href="#biblio-permissions">[PERMISSIONS]</a> that implementers can use for <a data-link-type="dfn" href="https://w3c.github.io/permissions/#new-information-about-the-users-intent" id="ref-for-new-information-about-the-users-intent"> explicit or implicit user consenting</a>. In addition, implementers are encouraged to use additional
-privacy enchancing mechanisms inline with their product requirements to provide a consistent and
+privacy-enhancing mechanisms inline with their product requirements to provide a consistent and
 cohesive experience. Such mechanisms can include, for example, global and per-origin access controls,
 page info dialogs, location bar indicators, or other disclosure user interface elements.</p>
     <p>The Generic Sensor API provides flexibility to implementers to make user consenting and