rlenferink commented on a change in pull request #21:
URL: https://github.com/apache/comdev-site/pull/21#discussion_r532238243
##########
File path: source/gettingStarted/101.md
##########
@@ -4,75 +4,77 @@ title: Getting started
# Where do I start?
-If you have no idea where to start with your engagement with an Apache project
+If you have no idea where to start your engagement with an Apache project,
this is the page for you.
### Finding the right project
-The key to working on projects at Apache (and any open source for that matter)
+The key to working on projects at Apache (and on any open source project, for
that matter)
is to have a personal reason for being involved. You might be trying to solve
a day job issue, you might be looking to learn a new technology or you might
simply want to do something fun in your free time. We don't care what your
motivation is we just care about you wanting to get involved.
If you don't have a specific technical issue to solve you might be willing to
work on any project. Our [projects page][1] provides a useful index which
-allows you to view projects alphabetically, by category or by language. When
you view a projects detail page in this list you will find details of their
+allows you to view projects alphabetically, by category or by coding language.
When you view a projects detail page in this list you will find information
about their
mailing lists, issue tracker and other resources.
-As well as our main projects you might also like to view our
+You might also like to view our
[Incubating projects][2]. These projects work in exactly the same way as our
"top
level projects" but are still developing their initial community.
-Once you've found some interesting looking projects join their mailing lists
and
+Once you've found some interesting-looking projects, join their mailing lists
and
start "lurking". Read the mails that come through the list. Initially you will
not
understand what people are talking about, but over time you will start to
-pick up the language, objectives, strategies and working patterns of the
community.
+pick up the language, objectives, strategies, concerns and working patterns of
the community.
#### Finding an issue to work on
-If you are trying to satisfy a specific technical problem then you already know
-what you want to work on, but if you are looking for something useful to do in
-order to participate in an ASF project then the projects issue/bug tracker is
your
-friend (this will be linked from the projects home page or from its entry on
the
+If you are trying to satisfy a specific technical problem, you already know
+what you want to work on; but if you are looking for something useful to do in
+order to participate in an ASF project, the projects issue/bug tracker is your
Review comment:
this should probably be `project's` as well
```suggestion
order to participate in an ASF project, the project's issue/bug tracker is
your
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
