Made some edits.

I don't think the following are clear and need to better understand to edit.

20- If you fix something for GitLab.com or one of our users, make sure that your solution becomes the default (preferred) method and radiate the information in the docs. We should run GitLab.com with the default settings and setup our users would also have.

26-We're a distributed company where people work remotely without missing out, prefer communication in public issues and chat channels and ensure conclusions of offline conversations are written down.

source/handbook/index.html

@@ -38,14 +38,15 @@ extra_css:
         <div class="general">
         <h2 id="general">General</h2>
           <ol>
-            <li>Working at GitLab B.V. is cooperating with the most talented people you've ever worked with, being the <b>most productive</b> you'll ever be, creating software that is helping the most people you've ever reached.</li>
+            <li>Working at GitLab, Inc. is cooperating with the most talented people you've ever worked with, being the most productive you'll ever be, and creating software that is helping the most people you've ever reached.</li>
             <li>We recognize that inspiration is perishable, if you’re <b>enthusiastic</b> about something that generates great results in relatively little time feel free to work on that.</li>
-            <li>Do what is right for our <b>customers</b> and the rest of the GitLab community, do what is best over the long term, don't be evil.</li>
+            <li>Do what is right for our <b>customers</b> and the rest of the GitLab community. Do what is best over the long term. Be kind.</li>
             <li>We create <b>simple</b> software to accomplish complex collaborative tasks.</li>
-            <li>Do <b>not</b> make jokes or unfriendly remarks about race, ethnic origin, skin colour, gender or sexual orientation.</li>
-            <li>Use <b>inclusive</b> language. For example, prefer 'Hi everybody' or 'Hi people' to 'Hi guys'.</li>
-            <li>Share problems you run into, ask for help, be forthcoming with information and <b>speak up</b>.</li>
+            <li>Refrain from making jokes or unfriendly remarks about race, religion, ethnic origin, skin color, gender or sexual orientation.</li>
+            <li>Use <b>inclusive</b> language. For example, we prefer 'Hi everybody' or 'Hi people' to 'Hi guys'.</li>
+            <li>Share problems you run into, ask for help, be forthcoming with information and <b>speak up. Ask questions in as public a way as possible so other people can learn as you learn.</b>.</li>
             <li>Work out in the <b>open</b>, try to use public issue trackers and repositories when possible.</li>
+            <li>If you need to ask a team member for help, please realize that there are other people in the community who do not know either. Be sure to document and radiate the answer/information to the entire community. After the question is answered, discuss where it should be documented and who will do the documenation. You can remind other people by asking where and who?</b>.</li>
             <li>Share solutions you find and answers you receive with the <b>whole community</b>.</li>
             <li>If you make a mistake, don't worry, correct it and <b>proactively</b> let the affected party, your team, and the CEO know what happened, how you corrected it and how, if needed, you changed the process to prevent future mistakes.</li>
             <li>You can always <b>refuse</b> to deal with people that treat you badly and get out of situations that make you feel uncomfortable.</li>
@@ -54,7 +55,7 @@ extra_css:
             <li>We want to have a great company so if you meet people that are <b>better</b> than yourself try to recruit them to join the company.</li>
             <li>It is easier to bond with people that have the same constraints, compensate for this and recognize that sales is hard because you are dependent on another organization and development is hard because you have to preserve the ability to quickly improve the product in the future.</li>
             <li>Our strategy is detailed in the <a href="https://docs.google.com/a/gitlab.com/document/d/1tco4-arhiA3V-XUJAkTtJ6zrfvT0OrUHtID2S1qVsXE/edit">GitLab Strategy document</a>, please read it and contribute.</li>
-            <li>Explicitly note what <b>next action</b> you propose or expect and from who.</li>
+            <li>Explicitly note what <b>next action</b> you propose or expect and from whom. This should be done in Issues, comments in Google docs, in emails, on Slack or other places that you communicate.</li>
             <li>There is no need for <b>consensus</b>, make sure that you give people that might have good insights a chance to respond (by /cc'ing them) but make a call yourself, <a href="https://twitter.com/sama/status/585950222703992833">consensus doesn't scale</a>.</li>
             <li>If you need to discuss with a team member for help please realize that probably the majority of the community also doesn't know, be sure to <b>document</b> the answer to radiate this information to the whole community. After the question is answered discuss where it should be documented and who will do it. You can remind other people of this by asking where/who?</li>
             <li>If you fix something for GitLab.com or one of our users make sure to make that the default (preferred) and radiate the information in the docs, we should run GitLab.com with the default settings and setup our users would also have.</li>
@@ -62,6 +63,7 @@ extra_css:
             <li>Be <b>kind</b> in your written communication, especially externally. Be constructive instead of argumentative or condescending.</li>
             <li>Everyone at the company cares about your output. Being away from the keyboard during the workday, doing private browsing or making personal phone calls is fine and encouraged.</li>
             <li>We're a distributed company where people work remote without missing out, prefer communication in public issues and chat channels and ensure conclusions of offline conversations are written down.</li>
+            <li>Assume best intentions.</li>
           </ol>
         </div>
         <div class="gitlab-workflow">