diff --git a/contrib/monitor/schemas.html b/contrib/monitor/schemas.html
index 4940b3b..d9c2aa5 100644
--- a/contrib/monitor/schemas.html
+++ b/contrib/monitor/schemas.html
@@ -241,7 +241,7 @@
                     // Loop results
                     $.each(schemasCount, function(schema, hits){
                         // IF TEST CONTINUE
-                        if(schema.substr(schema.length - 4) == 'test')
+                        if(schema.slice(-4) == 'test')
                             return;
 
                         var slug = makeSlug(schema);
diff --git a/schemas/README-EDDN-schemas.md b/schemas/README-EDDN-schemas.md
index 8423755..5568e2d 100644
--- a/schemas/README-EDDN-schemas.md
+++ b/schemas/README-EDDN-schemas.md
@@ -54,6 +54,16 @@ contents all Schemas specify a top-level JSON Object with the data:
    relevant README file within this documentation, e.g.
    [codexentry-README.md](./codexentry-README.md).
 
+Whilst currently (2022-11-23) the `gameversion` and `gamebuild` fields in the
+message `header` aren't yet mandatory in the sense of what's in the schema
+definitions, all Senders are **strongly encouraged** to send them.
+
+Indeed, the per-schema documentation, for every schema now states:
+
+#### gameversion and gamebuild
+You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild)
+of the Developers' documentation.
+
 ### General EDDN message outline
 
 Each `message` object must have, at bare minimum: