Revise installation and deployment steps in README

[priyanshu6238]

Updated installation and deployment instructions in README.

Summary by CodeRabbit

• Documentation
  • Added environment variable configuration instructions to the installation guide to help users properly set up .env files during project setup
  • Improved the Deployment section with clearer formatting and presentation of deployment commands
  • Standardized all code block examples throughout documentation by normalizing command formatting for consistent, improved readability and user experience

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The README.md file was updated to add an environment configuration installation step and standardize shell command formatting by removing leading prompt symbols throughout example code blocks.

Changes

Cohort / File(s)	Change Summary
Documentation Updates README.md	Added environment configuration step (copy .env.example to .env); removed leading $ prompt symbols from yarn and deployment command blocks for consistent presentation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Documentation-only changes with no code logic alterations
• Straightforward formatting normalization and addition of a setup instruction

Poem

🐰 A README so neat and refined,
With .env steps clearly assigned,
Those pesky dollar signs took flight—
Now commands align just right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately describes the main changes: revisions to installation and deployment steps in the README file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch priyanshu6238-patch-2

---

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.}

[github-actions]

🚀 Deployed on https://deploy-preview-527--glific-docs.netlify.app

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dd87519 and fc4cbaa.

📒 Files selected for processing (1)

• README.md (2 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

README.md

15-15: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

21-21: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

29-29: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

45-45: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (1)

README.md (1)

8-12: LGTM!

The new .env.example to .env installation step is well-documented with proper formatting and language specification. This improves the onboarding experience by explicitly guiding users to set up their environment configuration.