Skip to content

Commit f31a84f

Browse files
fix grammers
Signed-off-by: Rajesh-Nagarajan-11 <rajeshnagarajan36@gmail.com>
1 parent 0c7ad82 commit f31a84f

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

src/collections/handbook/community-roles/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Layer5 MeshMates are committed to helping community members be successful contri
100100

101101
Roles/Responsibilities:
102102

103-
Maintainers are those who are responsible for managing the growth and performance of the project. They are incharge of the project's wellbeing, reviewing and merging the PR, updating the libraries and dependencies in that project, monitoring the codebase and so much more.
103+
Maintainers are those who are responsible for managing the growth and performance of the project. They are in charge of the project's wellbeing, reviewing and merging the PR, updating the libraries and dependencies in that project, monitoring the codebase and so much more.
104104

105105
- Send a reminder about meetings
106106
- Prepare meetings

src/collections/handbook/community/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ import Point from "../code-of-conduct/bullet.svg";
2121

2222
Welcome to the Layer5 community! We're happy to have you here and handhold you for your first contribution. Here are some tips to help you get started:
2323

24-
<p><img className="logo" src={Point} alt="Point" /><strong>For Easy Identification -</strong> When setting up your slack workspace, your display name should be the same as your GitHub username for easy identification, engage freely, and in whatever form you will: as a listener, user, contributor, maintainer, ambassador, or bystander. Involvement in any way is warmly received.</p>
24+
<p><img className="logo" src={Point} alt="Point" /><strong>For Easy Identification -</strong> When setting up your Slack workspace, your display name should be the same as your GitHub username for easy identification, engage freely, and in whatever form you will: as a listener, user, contributor, maintainer, ambassador, or bystander. Involvement in any way is warmly received.</p>
2525
<p><img className="logo" src={Point} alt="Point" /><strong>Familiarize with the community -</strong> As you get to familiarize yourself with the community, know that there are multiple initiatives for you to explore. Some initiatives have working groups that meet at different times each week, while others use the weekly community meeting as their place of discussion. Details of each can be found on the <Link to="/community/calendar">community calendar</Link>. Everyone is welcome to join the calls and engage with other community members over Slack, the mailing list, and so on.</p>
2626
<p><img className="logo" src={Point} alt="Point" /><strong>Familiarize with the projects -</strong> The following is a sample of the many active, ongoing community projects. One way of doing so is to review the <Link to="/community/handbook/repository-overview">Layer5 Repository Overview</Link> section of this handbook to get a better understanding of each project. This document will help you to understand the projects based on their technology domain(s). Be sure to star the community's <a href="https://github.com/layer5io">repositories</a> on GitHub!</p>
2727
<p><img className="logo" src={Point} alt="Point" /><strong>Be friendly and open-minded -</strong> We encourage you to be welcoming to new collaborators and those just getting started. Other contributors might not have the same degree of experience or background as you, but that doesn't mean they can't provide useful ideas.</p>

src/collections/handbook/faq/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ A: To follow up on the community meetings, you can view and add the <a href="htt
3232
A: We might not get to everyone, but we try to elevate the works of all of our contributors. All of our community members are proud of their work and so are we! We want their work and names to be recognized across our collective technology industry. Be sure to follow and engage with the <a href="https://twitter.com/layer5">Twitter,</a><a href="https://www.youtube.com/channel/UCFL1af7_wdnhHXL1InzaMvA?sub_confirmation=1"> Youtube,</a> and <a href="https://www.linkedin.com/company/layer5/">Linkedin</a> accounts.
3333

3434
#### Q: I am not a coder, can I contribute too?
35-
A: Some community members join to contribute to open source projects, others jump in to put those projects to use, some are here to help cultivate and steward our community, while others are here just to hangout and absorb. All members are most welcome. Be sure to introduce yourself in the Layer5<a href="https://slack.layer5.io"> slack </a>and let other community members get acquainted with you and vice-versa.
35+
A: Some community members join to contribute to open source projects, others jump in to put those projects to use, some are here to help cultivate and steward our community, while others are here just to hangout and absorb. All members are most welcome. Be sure to introduce yourself in the Layer5<a href="https://slack.layer5.io"> Slack </a>and let other community members get acquainted with you and vice-versa.
3636

3737
#### Q: How should I approach assigning and working on issues within the community?
3838
A: To ensure efficiency and positive collaboration, please follow these guidelines:

0 commit comments

Comments
 (0)