diff --git a/files/en-us/mdn/contribute/howto/write_an_api_reference/sidebars/index.md b/files/en-us/mdn/contribute/howto/write_an_api_reference/sidebars/index.md
index b6b1430721f1e8c..e2822ffb67509a0 100644
--- a/files/en-us/mdn/contribute/howto/write_an_api_reference/sidebars/index.md
+++ b/files/en-us/mdn/contribute/howto/write_an_api_reference/sidebars/index.md
@@ -137,6 +137,6 @@ Further information about tag-based processing is available [in the APIRef sourc
 Once you've added an entry for your API into `GroupData.json`, submitted it as a pull request and had the change accepted into the main repo, you can include it in your API reference pages using the [`APIRef`](https://github.com/mdn/yari/blob/main/kumascript/macros/APIRef.ejs) macro, which takes the name you used for your API in GroupData as a parameter.
 As an example, the [WebVR API](/en-US/docs/Web/API/WebVR_API)'s sidebar is included in its pages with the following:
 
-```js
+```plain
 \{{APIRef("WebVR API")}}
 ```
diff --git a/files/en-us/mdn/structures/live_samples/index.md b/files/en-us/mdn/structures/live_samples/index.md
index aa2fc767d4d4f1f..e982ce670c4bc54 100644
--- a/files/en-us/mdn/structures/live_samples/index.md
+++ b/files/en-us/mdn/structures/live_samples/index.md
@@ -44,7 +44,7 @@ In many cases, you may be able to add the `EmbedLiveSample` or `LiveSampleLink`
 
 #### EmbedLiveSample macro
 
-```js
+```plain
 \{{EmbedLiveSample(block_ID, width, height, screenshot_URL, page_slug)}}
 ```
 
@@ -64,7 +64,7 @@ In many cases, you may be able to add the `EmbedLiveSample` or `LiveSampleLink`
 
 #### LiveSampleLink macro
 
-```js
+```plain
 \{{LiveSampleLink(block_ID, link_text)}}
 ```
 
diff --git a/files/en-us/mdn/structures/macros/index.md b/files/en-us/mdn/structures/macros/index.md
index 676421c0cd56278..a23bcb455754a95 100644
--- a/files/en-us/mdn/structures/macros/index.md
+++ b/files/en-us/mdn/structures/macros/index.md
@@ -22,7 +22,7 @@ Macros on MDN are implemented using server-executed [JavaScript](/en-US/docs/Web
 
 To use a macro, you enclose the call to the macro in a pair of double-braces along with its parameters, if any:
 
-```js
+```plain
 \{{macroname(parameter-list)}}
 ```
 
diff --git a/files/en-us/mdn/tools/kumascript/index.md b/files/en-us/mdn/tools/kumascript/index.md
index ab110fd308e188b..4e3a228c58a6b76 100644
--- a/files/en-us/mdn/tools/kumascript/index.md
+++ b/files/en-us/mdn/tools/kumascript/index.md
@@ -42,7 +42,7 @@ A script in KumaScript is a _template_, and each template is a file in [the macr
 
 Invoking a template is done with a _macro_, which can be used anywhere in any wiki content. Invoking the above template would look like this (provided it was saved in the macros directory with a filename of `hello.ejs`):
 
-```js
+```plain
 \{{hello(3)}}
 ```
 
@@ -58,7 +58,7 @@ Hello #2
 
 Macro syntax takes the following general form:
 
-```js
+```plain
 \{{templateName("arg0", "arg1", /* …, */ "argN")}}
 ```
 
@@ -73,7 +73,7 @@ Macro syntax follows these rules:
 
 As a semi-experimental feature (not guaranteed to work), you can supply a JSON object for the first and only parameter, like so:
 
-```js
+```plain
 \{{templateName({ "Alpha": "one", "Beta": ["a", "b", "c"], "Foo": "https:\/\/mozilla.org\/" })}}
 ```