updatd the links to gcs set up, setting up the bucket and adding media

[mahajantejas]

Summary by CodeRabbit

Documentation

• Updated prerequisite links in WhatsApp Groups Automation guides to reference the latest onboarding resources and Google Cloud setup documentation.
• Reorganized documentation structure for Google Sheets integration with improved guidance references.
• Clarified media sending feature prerequisites with updated documentation paths for cloud storage and file upload processes.

[coderabbitai]

Walkthrough

This PR updates documentation references across three WhatsApp Groups Automation guides, replacing outdated URLs with new Pre Onboarding documentation paths and restructuring Prerequisites sections for clarity.

Changes

Cohort / File(s)	Change Summary
Pre Onboarding Documentation Reference Updates docs/6. WhatsApp Groups Automation/Google Sheets Integration For WhatsApp Groups.md, docs/6. WhatsApp Groups Automation/Onboarding for new NGOs.md, docs/6. WhatsApp Groups Automation/WhatsApp Groups Automation Features.md	Updated Prerequisites sections to reference new Pre Onboarding documentation paths; replaced outdated Onboarding GCS links with updated URL anchors; restructured enumeration in Prerequisites for Google Sheets integration and media sending guidance

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Update 12. Link Google Sheets.md #423: Updates documentation to point to the Flow Actions/Link Google Sheets doc, which connects to the restructured Prerequisites section that now references this documentation.

Suggested reviewers

• Fawas003
• SangeetaMishr

Poem

🐰 Links refreshed with purpose clear,
Pre-onboarding docs brought near,
WhatsApp guides now unified,
All references realigned! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title Check	❓ Inconclusive	The pull request title "updatd the links to gcs set up, setting up the bucket and adding media" contains a typo ("updatd" instead of "updated") and is partially unclear in its phrasing. While the title does reference real aspects of the changes—specifically that documentation links related to GCS setup and media are being modified—the phrasing "setting up the bucket and adding media" is ambiguous and could suggest new functionality is being added rather than documentation references being updated. The title captures some of what was changed but lacks clarity about the primary action (updating documentation links to Pre Onboarding paths) and could mislead a teammate scanning the repository history.	Consider revising the title to be more precise and clear, such as "Update documentation links to Pre Onboarding GCS and media references" or "Fix broken links in WhatsApp Groups Automation documentation." This would better reflect that the changes are about updating/fixing documentation references rather than implementing new GCS or media functionality, and correcting the typo would ensure professionalism.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fixbrokenlinks-whatsappgroupsautomationpages

---

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-470--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 2e208da and 98b1514.

📒 Files selected for processing (3)

• docs/6. WhatsApp Groups Automation/Google Sheets Integration For WhatsApp Groups.md (1 hunks)
• docs/6. WhatsApp Groups Automation/Onboarding for new NGOs.md (1 hunks)
• docs/6. WhatsApp Groups Automation/WhatsApp Groups Automation Features.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/6. WhatsApp Groups Automation/Google Sheets Integration For WhatsApp Groups.md

[grammar] ~7-~7: There might be a mistake here.
Context: ... Prerequisites 1. Google cloud platform set up should be completed as per this [docume...

(QB_NEW_EN)

docs/6. WhatsApp Groups Automation/WhatsApp Groups Automation Features.md

[uncategorized] ~33-~33: “Google” is a proper noun and needs to be capitalized.
Context: ...te for sending media: 1. Should have a google cloud storage storage set up [refer her...

(A_GOOGLE)

---

[grammar] ~33-~33: There might be a mistake here.
Context: ...le%20Cloud%20Storage%20Setup%20-%20GCS). 2. Within the google cloud platform, should...

(QB_NEW_EN)

---

[uncategorized] ~34-~34: “Google” is a proper noun and needs to be capitalized.
Context: ...rage%20Setup%20-%20GCS). 2. Within the google cloud platform, should have a public bu...

(A_GOOGLE)

---

[uncategorized] ~35-~35: “Google” is a proper noun and needs to be capitalized.
Context: ...storage-bucket) 3. Upload files to the google cloud storage and generate the links [r...

(A_GOOGLE)

🔇 Additional comments (2)

docs/6. WhatsApp Groups Automation/Onboarding for new NGOs.md (1)

30-30: Link update looks good. Properly references the Pre Onboarding documentation path with correct URL encoding.

docs/6. WhatsApp Groups Automation/Google Sheets Integration For WhatsApp Groups.md (1)

7-8: Prerequisites restructuring improves clarity. Splitting the setup steps into two enumerated items with correct anchor references to specific documentation sections is a good improvement for user navigation.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix duplicate word and capitalization issues.

Three text quality issues need correction:

1. Line 33: "google cloud storage storage set up" contains a duplicate "storage" word.
2. Lines 33-35: "google" should be capitalized to "Google" (proper noun) in all three prerequisites.

Apply this diff:

-1. Should have a google cloud storage storage set up [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS).
-2.  Within the google cloud platform, should have a public bucket setup [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS#step-4-create-a-storage-bucket)
-3.  Upload files to the google cloud storage and generate the links [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/GCS%20Setup/Upload%20files%20on%20GCS)
+1. Should have a Google Cloud Storage set up [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS).
+2.  Within the Google Cloud Platform, should have a public bucket setup [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS#step-4-create-a-storage-bucket)
+3.  Upload files to Google Cloud Storage and generate the links [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/GCS%20Setup/Upload%20files%20on%20GCS)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	1. Should have a google cloud storage storage set up [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS).
	2. Within the google cloud platform, should have a public bucket setup [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS#step-4-create-a-storage-bucket)
	3. Upload files to the google cloud storage and generate the links [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/GCS%20Setup/Upload%20files%20on%20GCS)
	1. Should have a Google Cloud Storage set up [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS).
	2. Within the Google Cloud Platform, should have a public bucket setup [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/Google%20Cloud%20Storage%20Setup%20-%20GCS#step-4-create-a-storage-bucket)
	3. Upload files to Google Cloud Storage and generate the links [refer here](https://glific.github.io/docs/docs/Pre%20Onboarding/GCS%20Setup/Upload%20files%20on%20GCS)

🧰 Tools

🪛 LanguageTool

[uncategorized] ~33-~33: “Google” is a proper noun and needs to be capitalized.
Context: ...te for sending media: 1. Should have a google cloud storage storage set up [refer her...

(A_GOOGLE)

---

[grammar] ~33-~33: There might be a mistake here.
Context: ...le%20Cloud%20Storage%20Setup%20-%20GCS). 2. Within the google cloud platform, should...

(QB_NEW_EN)

---

[uncategorized] ~34-~34: “Google” is a proper noun and needs to be capitalized.
Context: ...rage%20Setup%20-%20GCS). 2. Within the google cloud platform, should have a public bu...

(A_GOOGLE)

---

[uncategorized] ~35-~35: “Google” is a proper noun and needs to be capitalized.
Context: ...storage-bucket) 3. Upload files to the google cloud storage and generate the links [r...

(A_GOOGLE)

🤖 Prompt for AI Agents

In docs/6. WhatsApp Groups Automation/WhatsApp Groups Automation Features.md
around lines 33 to 35, fix duplicate and capitalization errors: remove the
repeated word "storage" in "google cloud storage storage set up" and capitalize
"google" to "Google" in all three bullet points so each reads correctly (e.g.,
"Should have a Google Cloud Storage set up", "Within the Google Cloud Platform,
should have a public bucket set up", "Upload files to the Google Cloud Storage
and generate the links").