[comdev-site] branch master updated: Update guide-to-being-a-mentor.md

[so...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

solomax pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/comdev-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 182e209  Update guide-to-being-a-mentor.md
     new 87aa6d8  Merge pull request #35 from cottage14/patch-20
182e209 is described below

commit 182e209ed84f49360298854b92e391300b1b1711
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Mon Dec 7 09:58:18 2020 -0400

    Update guide-to-being-a-mentor.md
    
    Minor text edits
---
 source/guide-to-being-a-mentor.md | 61 +++++++++++++++++++--------------------
 1 file changed, 29 insertions(+), 32 deletions(-)

diff --git a/source/guide-to-being-a-mentor.md b/source/guide-to-being-a-mentor.md
index 16cf46a..0a48f69 100644
--- a/source/guide-to-being-a-mentor.md
+++ b/source/guide-to-being-a-mentor.md
@@ -5,7 +5,7 @@ title: guide to being a mentor
 <a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a>
 # Submitting ideas to the mentoring programme
 
-All ASF projects are invited to submit their ideas for consideration in the
+We invite all ASF projects to submit their ideas for consideration in the
 ASF mentoring programme. Any Apache member and experienced committers can
 submit ideas via JIRA (if your project does not use JIRA you can [use the Comdev Issue Tracker For GSoC Tasks](use-the-comdev-issue-tracker-for-gsoc-tasks.html). We are looking for as many interesting projects as we can come up with. 
 
@@ -13,29 +13,29 @@ submit ideas via JIRA (if your project does not use JIRA you can [use the Comdev
 ## Summary
 
 * Add an issue to JIRA (if your project does not use JIRA you can [use the Comdev Issue Tracker For GSoC Tasks](use-the-comdev-issue-tracker-for-gsoc-tasks.html)
-  * use sub-tasks if necessary
-* Label the main issue with "*mentor*" (these will show up at the [ASF wide list of issues](https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2021)%20AND%20labels%20in%20(mentor,%20Mentor)))
+  * Add sub-tasks if necessary
+* Label the main issue with "*mentor*" (these will show up at the [ASF-wide list of issues](https://issues.apache.org/jira/issues?jql=labels%20in%20(gsoc2021)%20AND%20labels%20in%20(mentor,%20Mentor)))
 * Label the main issue with "*gsoc2021*" if appropriate (these will show up at <https://s.apache.org/gsoc2021ideas>)
 
 <a name="guidetobeingamentor-Detail"></a>
-## Detail
+## Details
 
-To ensure you JIRA issues are included in our list of mentored projects
+To ensure we include your JIRA issues in our list of mentored projects,
 please add the label "mentor" to the issue. If you want it to be included
 in the Google Summer of Code lists also add the "gsoc" label. If you want
-to include a number of issues in a single mentored project please create a
+to include a number of issues in a single mentored project, please create a
 parent issue, label that one appropriately and add the other issues as
-sub-tasks, do not label each individual sub task as they will appear as
+sub-tasks. Do not label each individual sub-task as that would make them appear as
 separate tasks.
 
-If a mentor has been identified then please assign the issue to that
+If you have identifed a mentor, assign the issue to that
 mentor.
 
 ASF Members and committers can volunteer to mentor or co-mentor proposals.
-When in doubt about all this, contact mentors@community.apache.org.
+When in doubt about all this, contact `mentors@community.apache.org`.
 
 For more information about what it means to be a mentor and on how to write
-a proposal see:
+a proposal, see:
 
   - [GSoC Mentoring Guide](https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide)
   - [Gnome HowTo on mentoring](https://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/)
@@ -43,7 +43,7 @@ a proposal see:
 
 Note that interest, even by a qualified student, does not mean that any of
 those project will automatically go ahead. Depending on the number of
-projects; the number of people able to mentor and the timing we will
+projects; the number of people able to mentor, and the timing we will
 probably have to make a smaller selection.
 
 <a name="guidetobeingamentor-Publicisingyourmentoredissues"></a>
@@ -52,13 +52,13 @@ probably have to make a smaller selection.
 You can link to the [ASF wide list of issues](https://issues.apache.org/jira/secure/IssueNavigator.jspa?requestId=12315361)
  or you can create your own lists and feeds within your own website.
 
-Since your mentored issues are recorded alongside your normal issues you
+Since your mentored issues appear alongside your normal Jira issues, you
 can create and use filters to help people find them. You can provide RSS
 feeds, JSON exports and many more goodies for helping to get the message
 out.
 
-If you have any cool ideas for using this data please let us know so we can
-share them with other projects (mail dev@community.apache.org)
+If you have any cool ideas for using this data, let us know so we can
+share them with other projects (mail `dev@community.apache.org`).
 
 <a name="guidetobeingamentor-Examples"></a>
 ## Examples
@@ -70,47 +70,44 @@ share them with other projects (mail dev@community.apache.org)
 <a name="guidetobeingamentor-Stayingintouch"></a>
 # Staying in touch
 
-All mentors *must* subscribe to mentors@community.apache.org, our list for
+All mentors *must* subscribe to `mentors@community.apache.org`, our list for
 coordinating mentor activities. 
 
-Subscriptions to mentors will only be accepted from addresses known to
+We only accept subscriptions to mentors@ from addresses known to
 belong to ASF committers, so please use your @apache.org address to
-subscribe if possible, or at least an address that can be matched to your
-@apache.org address via the ASF's private/committers/info or
+subscribe if possible, or at least an address that we can match to your
+`@apache.org` address via the ASF's private/committers/info or
 private/committers/MailAlias.txt data.
 
-If you are interested in the mentor programme administration please also
-subscribe to dev@community.apache.org.
+If you are interested in mentor programme administration please also
+subscribe to `dev@community.apache.org`.
 
 If you are planning on mentoring as part of the GSoC programme you also
-need to register with Google, see our [GSoC](gsoc.html)
- page for more information.
+need to register with Google. See our [GSoC](gsoc.html) page for more information.
 
 <a name="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></a>
-## How much effort is involved with being a mentor
+## How much effort is involved with being a mentor?
 
-Most mentors spend between 3 and 5 hours per week with their students. Most
+Most mentors spend between three and five hours per week with their students. Most
 of this time is spent encouraging them.
 
 Within the ASF we like to think that the whole project community will help
-the student just as they would with any other community member. If your
-project is supportive in this way then you may be able to get away with
-less time. However, as mentor _you_ are responsible for evaluating the
+the student, just as they would any other community member. If your
+project is supportive in this way, you may be able to get away with spending
+less time yourself. However, as mentor _you_ are responsible for evaluating the
 student and helping them deliver on their commitments.
 
-The [GSoC Mentoring Guide](https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide)
- has plenty of useful materials for mentors.
+The [GSoC Mentoring Guide](https://developers.google.com/open-source/gsoc/resources/guide#mentor_guide) has plenty of useful materials for mentors.
 
 <a name="guidetobeingamentor-Anoteabouteligibility"></a>
 ## A note about eligibility
 
 If your project has any restrictions on who can participate (as is the case
-with Harmony for example) please be sure to clarify these with potential
+with Harmony, for example) be sure to clarify these with potential
 students as early as possible. It causes unnecessary confusion and
 disappointment if a student is awarded a slot but is later found to be
 ineligible. Don't rely on the fact that the student should have read
 details on the project web site. You must discuss their eligibility before
-offering to mentor them. Please also make a note in the webapp stating that
+offering to mentor them. Also make a note in the webapp stating that
 you have, as far as possible, confirmed the student is eligible to
 contribute.
-