From 0bfdb7cbf5a1057256538dea1e26ffcaf4a93a1b Mon Sep 17 00:00:00 2001
From: TrebledJ <39648915+TrebledJ@users.noreply.github.com>
Date: Sun, 1 Dec 2024 23:19:22 +0800
Subject: [PATCH] chore: copyedit

---
 .../prism-plugins-in-node/2024-11-03-prism-plugins-in-node.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/posts/programming/mini-projects/prism-plugins-in-node/2024-11-03-prism-plugins-in-node.md b/content/posts/programming/mini-projects/prism-plugins-in-node/2024-11-03-prism-plugins-in-node.md
index 4274561d2..b1ce5a8b7 100644
--- a/content/posts/programming/mini-projects/prism-plugins-in-node/2024-11-03-prism-plugins-in-node.md
+++ b/content/posts/programming/mini-projects/prism-plugins-in-node/2024-11-03-prism-plugins-in-node.md
@@ -20,7 +20,7 @@ Simple codeblocks suffice for most writers who need supporting text with pretty
 
 To tell a good story, the characters, plot, and location need to be clear to the audience. Similarly, blog posts and tutorials benefit from enhancements such as command-line demarcations, line numbers, labels, and inline markup.
 
-There are many cases where such codeblocks are warranted:
+There are many cases where such codeblocks are warranted (brackets contain remedial plugins):
 
 - Interaction: input and output should be contrasted, think: shell or Jupyter notebook (command-line)
 - A post compares or demonstrates a technique in multiple languages (show-language)