Merge pull request #2293 from /issues/2085/1

Fixes #2085. Fix remaining review typos.

webcompat/static/css/src/sub-nav.css

@@ -31,7 +31,7 @@
   width: 20px;
   height: 2em;
   position: absolute;
-  opacity: 0.7;
+  opacity: .7;
   margin-left: 3px;
 }
 

webcompat/templates/contributors/web-platform-research.html

@@ -23,7 +23,7 @@ <h1 id="research" class="headline-1 highlight">Web Platform Research</h1>
           <h2 id="implementations" class="headline-1 highlight">Implementations Differences</h2>
 
           <p>
-            Time to time, issues regarding Web compatibility are created by very specific implementation differences in one of the browsers. Either, an implementation bug or a vendor choice, it is worth to understand and document them.
+            From time to time, issues regarding Web compatibility are created by very specific implementation differences in one of the browsers. Either, an implementation bug or a vendor choice, it is worth to understand and document them.
           </p>
 
           <p>
@@ -36,7 +36,7 @@ <h2 id="implementations" class="headline-1 highlight">Implementations Difference
     </section>
     <section class="grid">
       <div class="grid-row">
-        <div class="grid-cell x3">   
+        <div class="grid-cell x3">
             <h2 id="surveys" class="headline-1 highlight">Web Platform Surveys</h2>
             <p>
               Browser vendors try to implement the Web as it currently exists. The Web standards try to give a direction for what the Web should be, but, at the same time, document its state. Having a better understanding on how a Web platform feature (DOM APIs, CSS, HTTP, …) is really used by Web developers becomes key for implementors. There are certain class of issues that are interesting to understand by exploring what Web developers use for creating the site. You may want to address this kind of work by running a survey on a specific feature that could ultimately help to improve the Web platform.