Update team.md #391
Update team.md #391
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
WalkthroughThe changes involve updates to the Changes
Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range and nitpick comments (1)
organized/docs/faq/team.md (1)
25-25: Improve clarity and politeness.The change to provide a specific email address improves clarity for potential contributors.
To further improve the politeness of the sentence, consider adding "please" as follows:
-To collaborate closely with the team, reach out via [support@organized-app.com](mailto:support@organized-app.com) email let us know about your interest in contributing. +To collaborate closely with the team, please reach out via [support@organized-app.com](mailto:support@organized-app.com) email and let us know about your interest in contributing.Tools
LanguageTool
[style] ~25-~25: This expression usually appears with a “please” in front of it.
Context: ...mailto:support@organized-app.com) email let us know about your interest in contributing.(INSERT_PLEASE)
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- organized/docs/faq/team.md (1 hunks)
Additional context used
LanguageTool
organized/docs/faq/team.md
[style] ~25-~25: This expression usually appears with a “please” in front of it.
Context: ...mailto:support@organized-app.com) email let us know about your interest in contributing.(INSERT_PLEASE)
Additional comments not posted (1)
organized/docs/faq/team.md (1)
19-19: LGTM!The addition of the biblical reference enhances the context of the quote and aligns well with the overall message.
|
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range and nitpick comments (1)
organized/docs/how-to-support/contribute.md (1)
37-37: Simplification of contact options looks good. Consider minor typographical improvements.The removal of the Telegram group link simplifies the contact options and focuses solely on email communication, which is a good change.
To further improve the readability of this section, consider the following suggestions from the static analysis tools:
- Shorten the phrase "send us an email" to "email us".
- Remove the comma between "Please" and "mention" or replace it with an em dash if you want to signal a pause.
-If you decide to contact us and propose your assistance in any of the mentioned areas, you can send us an email at [support@organized-app.com](mailto:support@organized-app.com). Please, mention the desired area of collaboration in your email topic. +If you decide to contact us and propose your assistance in any of the mentioned areas, you can email us at [support@organized-app.com](mailto:support@organized-app.com). Please mention the desired area of collaboration in your email topic.Tools
LanguageTool
[style] ~37-~37: In some texts, you can shorten this phrase. Consider using “email us”.
Context: ... in any of the mentioned areas, you can send us an email at [support@organized-app.com](mailto:s...(SEND_PRP_AN_EMAIL)
[typographical] ~37-~37: A comma between “please” and the verb is normally not needed. If you want to signal a pause, consider using an em dash instead.
Context: ...com](mailto:support@organized-app.com). Please, mention the desired area of collaboration in yo...(PLEASE_UNNECESSARY_COMMA)
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- organized/docs/how-to-support/contribute.md (1 hunks)
Additional context used
LanguageTool
organized/docs/how-to-support/contribute.md
[style] ~37-~37: In some texts, you can shorten this phrase. Consider using “email us”.
Context: ... in any of the mentioned areas, you can send us an email at [support@organized-app.com](mailto:s...(SEND_PRP_AN_EMAIL)
[typographical] ~37-~37: A comma between “please” and the verb is normally not needed. If you want to signal a pause, consider using an em dash instead.
Context: ...com](mailto:support@organized-app.com). Please, mention the desired area of collaboration in yo...(PLEASE_UNNECESSARY_COMMA)
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
Checklist: