Editorial: Remove "non-standard" from abstract.

Also, get rid of an old issue that seems less relevant.

Fixes: #165

compatibility.bs

@@ -4,7 +4,7 @@ H1: Compatibility
 Shortname: compat
 Text Macro: TWITTER compatstandard
 Text Macro: LATESTRD 2021-12
-Abstract: This standard describes a collection of non-standard (and often vendor-prefixed) CSS properties and DOM APIs that web browsers need to support for compatibility with the de facto web.
+Abstract: This standard describes a collection of (often vendor-prefixed) CSS properties and DOM APIs that web browsers need to support for compatibility with the de facto web.
 Translation: ja https://triple-underscore.github.io/compat-ja.html
 Indent: 2
 Markup Shorthands: dfn yes
@@ -64,10 +64,6 @@ There exists an increasingly large corpus of web content that depends on web bro
 
 This specification aims to describe the minimal set of <code>webkit</code>-prefixed CSS properties and DOM APIs that user agents are required to support for web compatibility.
 
-<div class="XXX">
-The <a href="https://wiki.mozilla.org/Compatibility/Mobile/Non_Standard_Compatibility">Non-Standard Compatibility</a> wiki page will serve as a rough guide for what this specification intends to cover.
-</div>
-
 <h2 id='conformance'>Conformance</h2>
 All diagrams, examples, and notes in this specification are
 non-normative, as are all sections explicitly marked non-normative.