You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dm...@apache.org on 2020/03/11 22:31:45 UTC

svn commit: r1875106 - /ignite/site/branches/ignite-redisign/community/contribute.html

Author: dmagda
Date: Wed Mar 11 22:31:45 2020
New Revision: 1875106

URL: http://svn.apache.org/viewvc?rev=1875106&view=rev
Log:
updated contributed page

Modified:
    ignite/site/branches/ignite-redisign/community/contribute.html

Modified: ignite/site/branches/ignite-redisign/community/contribute.html
URL: http://svn.apache.org/viewvc/ignite/site/branches/ignite-redisign/community/contribute.html?rev=1875106&r1=1875105&r2=1875106&view=diff
==============================================================================
--- ignite/site/branches/ignite-redisign/community/contribute.html (original)
+++ ignite/site/branches/ignite-redisign/community/contribute.html Wed Mar 11 22:31:45 2020
@@ -81,9 +81,9 @@ under the License.
                 the contributors' list.
             </p>
             <p>
-                Last, check <a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Collaborate" target="_blank">
+                Next, check <a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Collaborate" target="_blank">
                 How to Collaborate</a> page for more details on various communication channels used by the community
-                members. Even though most of the discussions take place on the dev list, we hang out in Slack.
+                members. Even though most of the discussions take place on the dev list, we hang out on Slack.
             </p>
 		
 			<h2>Contribute by Helping Others</h2>
@@ -102,16 +102,16 @@ under the License.
 
             <h2>Contribute Documentation Changes</h2>
             <p>
-                Technical documentation and API references such as JavaDocs are as valuable as contribution of bug
-                fixes or features. Ignite documentation is an integral part of the project that educates Ignite users
+                Contributing to technical documentation and API references such as JavaDocs are as valuable as contributing to bug
+                fixes or features. Ignite documentation is an integral part of the project, which educates Ignite users
                 about Ignite capabilities, configuration techniques, optimization aspects and many other areas they need
-                to know to deploy Ignite successfully in production. Documentation and APIs are the faces of the
-                project and the community puts a lot of efforts maintaining them properly and professionally.
+                to understand to deploy Ignite successfully in production. Documentation and APIs are the faces of the
+                project and the community puts a lot of effort in maintaining them properly and professionally.
             </p>
             <p>
                 Code changes contribution is not the only way to become an Ignite committer. Help the community to
                 produce and maintain the documentation pages or API references, edit and correct existing content, stay
-                active on the user and dev mailing lists, and you'll become a committer inevitably.
+                active on the user and dev mailing lists, and you'll become a committer in due course.
             </p>
 		
 			<ul class="page-list">
@@ -143,8 +143,8 @@ under the License.
             <p>
                 Ignite is used together with a huge selection of libraries and
                 frameworks, and some of them are officially supported by the community. While some of the
-                existing integrations such as with Spark, Spring Data or Hibernate still reside in the primary Ignite
-                repository, they all will be eventually moved to Ignite Extensions repository. New integrations are
+                existing integrations such as with Spark, Spring Data, or Hibernate still reside in the primary Ignite
+                repository, they all will eventually be moved to the Ignite Extensions repository. New integrations are
                 accepted to the Extensions repository only.
             </p>
             <p>
@@ -168,9 +168,8 @@ under the License.
             
             <h2>Contribute to Ignite core</h2>
             <p>
-                If you are willing to contribute to the core components of Ignite then consider one of the tickets
-                below. Those are the tickets of easy and moderate complexity community members prepared for you to
-                simplify your start:
+                If you want to contribute to the core components of Ignite, then consider one of the tickets
+                below. These tickets are of easy and moderate complexity, which can simplify your start:
             </p>
             <ul class="page-list">
                 <li>
@@ -235,10 +234,10 @@ under the License.
                 The "ignite-{version}" branch contains the latest code for the latest or upcoming release.
 
                 Refer to the <a href="https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute" target="_blank">Contribution and
-                Development</a> page that explains the process in detail including reviews, pull-requests, etc. --
-                everything you need to know and to do before a contribution can be accepted.
-                While below you can find quick instructions if you can't wait and want to checkout the Ignite repo,
-                explore its code and do some changes:
+                Development</a> page which explains the process in detail including reviews, pull-requests, etc. --
+                everything you need to know and do before a contribution can be accepted.
+                While below you can find more detailed instructions, here is how you can checkout the Ignite repo and explore
+                its code:
             </p>
             <h5>GIT checkout</h5>
             <pre class="brush:bash">