docs: fixes fuzz from last merge (#801)

Signed-off-by: Adrian Cole <adrian@tetrate.io>

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,5 +1,5 @@
 ---
-name: CoreFeature Request
+name: Feature Request
 about: Suggest an idea for wazero to support.
 title: ''
 labels: enhancement

site/content/languages/go.md

@@ -34,7 +34,7 @@ Due to lack of adoption, support and relatively high implementation overhead,
 most choose [TinyGo]({{< relref "/tinygo.md" >}}) to compile source code, even if it supports less
 features.
 
-## WebAssembly CoreFeatures
+## WebAssembly Features
 
 `GOARCH=wasm GOOS=js` uses instructions in [WebAssembly Core Specification 1.0]
 [15] unless `GOWASM` includes features added afterwards.

site/content/specs.md

@@ -47,13 +47,13 @@ Format, e.g. compiling `.wat` files. Users can work around this using tools such
 compile the text format into the binary format. In practice, the text format is
 too low level for most users, so delays here have limited impact.
 
-#### Post 2.0 CoreFeatures
-CoreFeatures regardless of W3C release are inventoried in the [Proposals][10].
+#### Post 2.0 Features
+Features regardless of W3C release are inventoried in the [Proposals][10].
 repository. wazero implements [Finished Proposals][11] based on user demand,
-using [wazero.RuntimeConfig][7] feature flags. As of mid 2022, all finished proposals
-are included in [2.0][14] Working Draft.
+using [wazero.RuntimeConfig][7] feature flags. As of late 2022, all finished
+proposals are included in [2.0][14] Working Draft.
 
-CoreFeatures not yet assigned to a W3C release are not reliable. Encourage the
+Features not yet assigned to a W3C release are not reliable. Encourage the
 [WebAssembly community][12] to formalize features you rely on, so that they
 become assigned to a release, and reach the W3C recommendation (REC) phase.