fix trivial typos

faq.html

@@ -49,9 +49,9 @@ <h1>FAQs</h1>
               <div>
                 <p>The Physical Web’s core value proposition is to enable users to have information at their fingertips no matter their physical context. This information can take the form of a simple static web page to a more robust web application. A few examples might include:</p><br>
                 <ul>
-                  <li>A dog collar could allow passerby to call a service to find the owner</li>
-                  <li>A bus that could alert users of its next stop</li>
-                  <li>A city rent-a-bike service could enable users to sign up on the spot</li>
+                  <li>A dog collar could allow passerby to call a service to find the owner.</li>
+                  <li>A bus that could alert users of its next stop.</li>
+                  <li>A city rent-a-bike service could enable users to sign up on the spot.</li>
                   <li>A home appliance could offer an interactive tutorial.</li>
                   <li>An industrial robot could display diagnostic information.</li>
                   <li>A mall that could offer a map.</li>
@@ -67,9 +67,9 @@ <h1>FAQs</h1>
               </div>
             </li>
             <li>
-              <a class="toggle-faq">Why does Physical Web used Bluetooth Low Energy? </a>
+              <a class="toggle-faq">Why does Physical Web use Bluetooth Low Energy? </a>
               <div>
-                <p>There are many ways to broadcast a URL. Today, the Physical Web uses Bluetooth Low Energy (BLE) because of its ubiquity on mobile devices today. Additionally, it is highly energy efficient -- many bluetooth beacons today have multi-year battery lives.</p><br>
+                <p>There are many ways to broadcast a URL. Today, the Physical Web uses Bluetooth Low Energy (BLE) because of its ubiquity on mobile devices. Additionally, it is highly energy efficient -- many bluetooth beacons today have multi-year battery lives.</p><br>
                 <p>However, this does not preclude the possibility of Physical Web catering to alternate transport protocols in the future. Early potential options include mDNS and uPnP over WiFi.</p>
               </div>
             </li>
@@ -89,7 +89,7 @@ <h1>FAQs</h1>
                 <ul>
                   <li>Certain implementations of the Physical Web require that the broadcast URL be over HTTPS (e.g. Chrome, Nearby Notifications)</li>
                   <li>The URL could be obfuscated (e.g. using a non-branded domain)</li>
-                  <li>A rotating token on the beacon would constantly alter the URL</li>
+                  <li>A rotating token on the beacon could constantly alter the URL</li>
                   <li>The web page could require a login</li>
                 </ul>