Fix incorrect Windows command and add Chrome/Chromium label to clearing cache instructions

[demarco2016]

Closes #413

Bug 1: Incorrect Windows command

• Changed ind to indstr in Windows port conflict resolution command
• ind requires quoted search strings and cannot filter port numbers correctly on Windows

Bug 2: Chrome-specific instructions not labeled

• Added "(Chrome/Chromium)" label to the cache clearing instructions
• The "Click on the left of your address bar -> Cookies and site data..." steps only work on Chrome/Chromium, not Firefox, Brave, or Safari

Summary by CodeRabbit

• Documentation
  • Clarified browser cache clearing instructions for Chrome/Chromium with step-by-step navigation path.
  • Improved Windows port-conflict troubleshooting command for better accuracy.

[netlify]

✅ Deploy Preview for genlayer-docs ready!

Name	Link
🔨 Latest commit	ba895f7
🔍 Latest deploy log	https://app.netlify.com/projects/genlayer-docs/deploys/6a070199e7ae890008ffadf5
😎 Deploy Preview	https://deploy-preview-414--genlayer-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3f11656c-b9c6-4d1f-9935-023fc3bcebdd

📥 Commits

Reviewing files that changed from the base of the PR and between 9350f95 and ba895f7.

📒 Files selected for processing (1)

• pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx

---

📝 Walkthrough

Walkthrough

This PR updates the GenLayer Studio troubleshooting documentation to fix two issues: clarifying the cache-clearing steps for Chrome/Chromium browsers and correcting the Windows command for identifying port conflicts from find to findstr.

Changes

Troubleshooting Guide Updates

Layer / File(s)	Summary
Chrome/Chromium cache clearing instructions pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx	Expanded the cache clearing bullet to include explicit browser UI navigation steps (address bar → Cookies and site data → Manage on device → Delete localhost) specific to Chrome/Chromium.
Windows port detection command pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx	Updated the netstat filtering command from find <PORT_NUMBER> to findstr <PORT_NUMBER> to use the correct Windows command for string matching.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through docs with care,
Two troublesome bugs we'll repair,
Chrome's cache now clear, the path so bright,
Windows finds its ports just right,
GenLayer studio shines with all might! 🐰✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description does not follow the Conventional Commits format specified in the template. The description lacks a properly formatted commit-style title with type and scope.	Reformat the title to use Conventional Commits format, e.g., 'fix(troubleshooting): correct Windows command and label Chrome-specific cache instructions'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the two main changes: fixing the Windows command and adding Chrome/Chromium label to cache clearing instructions.
Linked Issues check	✅ Passed	The PR successfully addresses both objectives from issue #413: correcting the Windows command from 'find' to 'findstr' and adding Chrome/Chromium label to cache clearing instructions.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly related to the two bugs specified in issue #413; no out-of-scope modifications are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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 and usage tips.}

[demarco2016]

Hi team, the issues are resolved now. I received the email and everything looks good. Ready for review. Thanks

[demarco2016]

@coderabbitai, thanks for the review. This was my first PR to this repo I'll follow the Conventional Commits format next time. Appreciate the feedback

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@demarco2016 Welcome, and great first contribution! 🎉 Fixing real documentation bugs like the findstr command and the browser-specific cache instructions is genuinely helpful for users. Looking forward to your next PRs — and yes, sticking to the Conventional Commits format (e.g., fix: correct Windows findstr command in troubleshooting) will help the maintainers keep the changelog clean. Thanks for being receptive to the feedback!

(´｡• ᵕ •｡`) ♡

---

✏️ Learnings added

Learnt from: demarco2016
URL: https://github.com/genlayerlabs/genlayer-docs/pull/414

Timestamp: 2026-05-16T11:28:34.718Z
Learning: The genlayerlabs/genlayer-docs repository follows the Conventional Commits format for PR titles and commit messages (e.g., `fix: description`, `docs: description`, `feat: description`). Flag PR titles or commits that do not follow this convention.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.