[incubator] branch master updated: Update community.ad

[jm...@apache.org]

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

jmclean pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator.git


The following commit(s) were added to refs/heads/master by this push:
     new bd7d6f228 Update community.ad
     new a297ab7ab Merge pull request #108 from cottage14/patch-30
bd7d6f228 is described below

commit bd7d6f2281dcc426c735970e282fbabab6370e6d
Author: Andrew Wetmore <an...@cottage14.com>
AuthorDate: Mon Apr 17 14:45:21 2023 -0300

    Update community.ad
    
    line 45: added missing letter
    line 47: added missing letter. Changed 'forum' to 'list' in two places, as the topic is mailing lists.
---
 pages/guides/community.ad | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/guides/community.ad b/pages/guides/community.ad
index 66f5be76e..5343f3eb9 100644
--- a/pages/guides/community.ad
+++ b/pages/guides/community.ad
@@ -42,9 +42,9 @@ Private communications tend to be more candid but also more likely to be ill-jud
 
 Communication through other channels also reduces the chance of link:http://en.wikipedia.org/wiki/Serendipity[serendipity]. As with most social networks, most subscribers to a email list never post and most posts come from a tiny minority of subscribers. Some passive subscribers are just interested in where the project is going. But others understand related fields and have a limited intersection of interest. This second group will often post when a topic in which they are interested ari [...]
 
-If a project uses alternative forms of communication, it is essential to try to minimize the chances of problems arising. All matters of substance need to move back to the email lists. Projects need to preserve, and post back to the lists, significatn conversation threads in other channels. Project should post regular reminders that other secondary forms of communication exist.
+If a project uses alternative forms of communication, it is essential to try to minimize the chances of problems arising. All matters of substance need to move back to the email lists. Projects need to preserve, and post back to the lists, significatn conversation threads in other channels. Projects should post regular reminders that other secondary forms of communication exist.
 
-There is a limited number of topics, such as security issues and discussions about people, which it is best to handl in private. As much business of the project as possible should take place on public lists, but the private list is available for matters of a sensitive nature. Good netiquette requires that you seek permission from the poster before making public posts made to a private list. Try to avoid cross-posting between public and private forums. Take care not to post a reply to a p [...]
+There is a limited number of topics, such as security issues and discussions about people, which it is best to handle in private. As much business of the project as possible should take place on public lists, but the private list is available for matters of a sensitive nature. Good netiquette requires that you seek permission from the poster before making public posts made to a private list. Try to avoid cross-posting between public and private lists. Take care not to post a reply to a p [...]
 
 Learning to use email lists effectively is very important. If your project community can achieve this, it has a good chance to be lively, active and thriving. The future looks bright.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org