Playbook-guide update

.devcontainer/Dockerfile

@@ -1,4 +1,4 @@
-FROM node:22-alpine
+FROM node:24-alpine
 RUN apk add --no-cache \
   git \
   openssh \

.github/workflows/main.yml

@@ -10,16 +10,16 @@ jobs:
     permissions:
       contents: read
     steps:
-      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
+      - uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
         with:
           persist-credentials: false
-      - uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+      - uses: actions/setup-node@2028fbc5c25fe9cf00d9f06a71cc4710d4507903 # v6.0.0
         with:
-          node-version: 22
+          node-version: 24
           cache: npm
       - run: npm ci
       - run: npm run build
-      - uses: actions/upload-pages-artifact@56afc609e74202658d3ffba0e8f6dda462b719fa # v3.0.1
+      - uses: actions/upload-pages-artifact@7b1f4a764d45c48632c6b24a0339c27f5614fb0b # v4.0.0
         with:
           path: docs/.vuepress/dist
 

docs/playbook-guide.md

@@ -144,8 +144,10 @@ Remember these when checking language issues:
   and flag any that don't match the sentence's intended meaning or grammatical structure.
 - When reviewing lists, ensure all items are punctuated consistently, whether with commas, semicolons, or no punctuation at all.
 - When looking at the source code, understand that ' equals to apostrophe
-- Find space-will-be-missing issues when reviewing .tsx files. Carefully check every line that ends with a closing HTML tag (like `</em>`, `</strong>`,
-  `</a>`, etc.) - if text continues on the immediately following line without any explicit space character or JSX space expression `{" "}`, this will cause missing spaces in the rendered output. See the examples below.
+- Find space-will-be-missing issues when reviewing .tsx files. In JSX, whitespace-only lines between text content are stripped. Only flag an issue if BOTH:
+  1. A line ends with a closing tag (like `</em>`, `</strong>`, `</a>`) with nothing after it (no space, no `{" "}`, no other text) before the line break
+  2. The next line starts with any text other than punctuation or an opening tag
+     Do NOT flag if the closing tag is followed by space, `{" "}`, or any other text on the same line. See the examples below.
 
 Space-will-be-missing issue examples