-
Notifications
You must be signed in to change notification settings - Fork 9
Update 03. Setup an organisation on GupShup.md #321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
added the new step of adding Partner ID in gupshup steps
WalkthroughThe documentation for setting up an organization on GupShup has been thoroughly revised and expanded. The update introduces a step-by-step, illustrated onboarding guide, adds a YouTube video tutorial, and incorporates detailed procedural instructions, screenshots, and external resource links, transforming the document into a comprehensive setup manual. Changes
Poem
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
🚀 Deployed on https://deploy-preview-321--glific-docs.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (7)
docs/2. Onboarding/03. Setup an organisation on GupShup.md (7)
4-8: Use Markdown headings and ensure responsive video embed
Instead of raw HTML<h1>/<h4>, use Markdown syntax (e.g.,# Video Tutorial) to stay consistent with the rest of the docs. Also consider making the iframe responsive (e.g., wrapping it in a container with a max-width or using a Markdown video embed helper) so it displays nicely on mobile devices.
14-14: Correct grammar and simplify phrasing
Change “an phone number” to “a phone number” and replace “so as to receive” with “to receive” for clearer, more concise English.🧰 Tools
🪛 LanguageTool
[misspelling] ~14-~14: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ness%20API/) 1. A new phone number or an phone number that hasn’t been used with...(EN_A_VS_AN)
[style] ~14-~14: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”.
Context: ...should be activated with a minimal plan so as to receive sms verification code/call from...(SO_AS_TO)
28-28: Improve clarity and punctuation
Add a space in “Google (preferred)”, capitalize “email ID”, and rephrase the tail to something like:“…using a common email ID like
info@glific.orgso multiple team members can access it if something goes wrong.”
30-30: Consistent casing for 'sign up'
Use the verb form “sign up” instead of the noun “Signup” (e.g., “Complete the sign-up”).
35-38: Refine email and login wording
- Change “A verification mail” to “A verification email”.
- Merge the two sentences and correct the verb:
“Once verification is complete, please log in using your credentials.”
🧰 Tools
🪛 LanguageTool
[misspelling] ~36-~36: Did you mean the verb “log in” instead of the noun ‘login’?
Context: ...nt. Once verification is done. Please login using the credentials. 
58-58: Clarify naming constraints
Rephrase “(No space or special characters allowed)” to “(No spaces or special characters are allowed)” for grammatical consistency.
182-182: Add missing comma for clarity
Insert a comma before “and” in the sentence:“…take 3-4 working days to review, and you will receive an email once this is done.”
🧰 Tools
🪛 LanguageTool
[uncategorized] ~182-~182: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ook will take 3-4 working days to review and you will receive an email once this is ...(COMMA_COMPOUND_SENTENCE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/2. Onboarding/03. Setup an organisation on GupShup.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/2. Onboarding/03. Setup an organisation on GupShup.md
[misspelling] ~14-~14: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ness%20API/) 1. A new phone number or an phone number that hasn’t been used with...
(EN_A_VS_AN)
[style] ~14-~14: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”.
Context: ...should be activated with a minimal plan so as to receive sms verification code/call from...
(SO_AS_TO)
[misspelling] ~36-~36: Did you mean the verb “log in” instead of the noun ‘login’?
Context: ...nt. Once verification is done. Please login using the credentials. 
[uncategorized] ~182-~182: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ook will take 3-4 working days to review and you will receive an email once this is ...
(COMMA_COMPOUND_SENTENCE)
🔇 Additional comments (4)
docs/2. Onboarding/03. Setup an organisation on GupShup.md (4)
23-23: Step 1 instruction looks good
The “Next, go to GupShup.io and click on sign up” step is clear and correctly formatted.
25-25: Skip
The screenshot embed appears correctly formatted and functional.
32-32: Skip
The screenshot embed is fine; just ensure the alt text accurately describes the content for accessibility.
62-62: Skip
The screenshot embed is correctly formatted; just double-check that the alt text describes the image.
| 6. Please fill in the **Company/Organization details.** | ||
|
|
||
|  | ||
|
|
||
|
|
||
| 6. Click on the `Create your first App` button. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix duplicate step numbers
You have two steps numbered “6.” (fill company details and create first App). This will confuse readers. Renumber the second occurrence as step 7 (and increment all subsequent steps accordingly).
added the new step of adding Partner ID in gupshup steps
Summary by CodeRabbit