Skip to content

Commit 6d18e2f

Browse files
authored
Merge pull request #3604 from lavanitha/main
Fix minor typos and spacing in contribution guide
2 parents 0ee9daf + 6f40173 commit 6d18e2f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

_articles/how-to-contribute.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ related:
1414

1515
<aside markdown="1" class="pquote">
1616
<img src="https://avatars.githubusercontent.com/errietta?s=180" class="pquote-avatar" alt="avatar">
17-
Working on \[freenode\] helped me earn many of the skills I later used for my studies in university and my actual job. I think working on open source projects helps me as much as it helps the project!
17+
Working on [freenode] helped me earn many of the skills I later used for my studies in university and my actual job. I think working on open source projects helps me as much as it helps the project!
1818
<p markdown="1" class="pquote-credit">
1919
[@errietta](https://github.com/errietta), ["Why I love contributing to open source software"](https://www.errietta.me/blog/open-source/)
2020
</p>
@@ -26,15 +26,15 @@ Why do people contribute to open source? Plenty of reasons!
2626

2727
### Improve software you rely on
2828

29-
Lots of open source contributors start by being users of software they contribute to. When you find a bug in an open source software you use, you may want to look at the source to see if you can patch it yourself. If that's the case, then contributing the patch back is the best way to ensure that your friends (and yourself when you update to the next release) will be able to benefit from it.
29+
Lots of open source contributors start by being users of software they contribute to. When you find a bug in open source software you use, you may want to look at the source to see if you can patch it yourself. If that's the case, then contributing the patch back is the best way to ensure that your friends (and yourself when you update to the next release) will be able to benefit from it.
3030

3131
### Improve existing skills
3232

3333
Whether it's coding, user interface design, graphic design, writing, or organizing, if you're looking for practice, there's a task for you on an open source project.
3434

3535
### Meet people who are interested in similar things
3636

37-
Open source projects with warm, welcoming communities keep people coming back for years. Many people form lifelong friendships through their participation in open source, whether it's running into each other at conferences or late night online chats about burritos.
37+
Open source projects with warm, welcoming communities keep people coming back for years. Many people form lifelong friendships through their participation in open source, whether it's running into each other at conferences or late-night online chats about burritos.
3838

3939
### Find mentors and teach others
4040

@@ -48,7 +48,7 @@ By definition, all of your open source work is public, which means you get free
4848

4949
Open source offers opportunities to practice leadership and management skills, such as resolving conflicts, organizing teams of people, and prioritizing work.
5050

51-
### It's empowering to be able to make changes, even small ones
51+
### Its empowering to make changes, even small ones
5252

5353
You don't have to become a lifelong contributor to enjoy participating in open source. Have you ever seen a typo on a website, and wished someone would fix it? On an open source project, you can do just that. Open source helps people feel agency over their lives and how they experience the world, and that in itself is gratifying.
5454

@@ -95,7 +95,7 @@ Even if you like to write code, other types of contributions are a great way to
9595

9696
<aside markdown="1" class="pquote">
9797
<img src="https://avatars.githubusercontent.com/kittens?s=180" class="pquote-avatar" alt="avatar">
98-
Seriously, \[documentation\] is mega-important. The documentation so far has been great and has been a killer feature of Babel. There are sections that could certainly use some work and even the addition of a paragraph here or there is extremely appreciated.
98+
Seriously, documentation is mega-important. The documentation so far has been great and has been a killer feature of Babel. There are sections that could certainly use some work and even the addition of a paragraph here or there is extremely appreciated.
9999
<p markdown="1" class="pquote-credit">
100100
@kittens, ["Call for contributors"](https://github.com/babel/babel/issues/1347)
101101
</p>
@@ -390,7 +390,7 @@ Whether you're a one-time contributor or trying to join a community, working wit
390390

391391
<aside markdown="1" class="pquote">
392392
<img src="https://avatars.githubusercontent.com/shubheksha?s=180" class="pquote-avatar" alt="avatar">
393-
\[As a new contributor,\] I quickly realized I had to ask questions if I wanted to be able to close the issue. I skimmed through the code base. Once I had some sense of what was going on, I asked for more direction. And voilà! I was able to solve the issue after getting all the relevant details I needed.
393+
[As a new contributor,] I quickly realized I had to ask questions if I wanted to be able to close the issue. I skimmed through the code base. Once I had some sense of what was going on, I asked for more direction. And voilà! I was able to solve the issue after getting all the relevant details I needed.
394394
<p markdown="1" class="pquote-credit">
395395
@shubheksha, [A Beginner's Very Bumpy Journey Through The World of Open Source](https://www.freecodecamp.org/news/a-beginners-very-bumpy-journey-through-the-world-of-open-source-4d108d540b39/)
396396
</p>

0 commit comments

Comments
 (0)