Fix formatting in Node installation docs

[alirezanikanzadeh]

Why

Fix a formatting issue in the Node installation guide where the sudo systemctl status pg-node line was incorrectly fenced, causing the command not to render as intended.

What/Approach

Removed the stray code-fence markers around the status command so the command appears inline and renders correctly.

Notes

Docs-only change; no code changes or behavior impact. No testing required.

Summary by CodeRabbit

• Documentation
  • Updated the installation guide to display the systemctl status pg-node command as inline content instead of a code block.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f657bfc-0404-4680-87bc-191a480f92ac

📥 Commits

Reviewing files that changed from the base of the PR and between 2e5a15b and c644868.

📒 Files selected for processing (1)

• content/docs/en/node/installation.mdx

💤 Files with no reviewable changes (1)

• content/docs/en/node/installation.mdx

---

Walkthrough

The installation guide removes the Markdown code fence around systemctl status pg-node. The command text remains unchanged.

Changes

Installation documentation

Layer / File(s)	Summary
Service-status command formatting content/docs/en/node/installation.mdx	The surrounding Markdown code fence is removed. The systemctl status pg-node command remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

I’m a rabbit with a tidy guide,
I nibbled the fence from the command inside.
systemctl status pg-node stays clear,
With cleaner Markdown hopping here.
Snip, snip—documentation is bright!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the documentation formatting change in the Node installation guide.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[alirezanikanzadeh]

Thanks for the automated summary — helpful! This is a docs-only formatting fix (no behavior change). Ready for merge once CI/checks complete.