Corrections.

docs/misc/organisation.md

@@ -1,34 +1,32 @@
 # LUYA as an organisation
 
-## 1. Legal Form
+## 1. Legal form
 
-+ Is not bound to any company or private person.
-+ Decisions, which are not covered by 2), will be taken democratically among the members entitled to vote.
++ LUYA as a product and as an organisation is not owned by any company or private person.
++ Decisions not covered by [Long-term intention and objectives](#2-long-term-intention-and-objectives) will be taken democratically among the members entitled to vote.
 
-## 2. Long-term intention and objectives
+## 2. Long-term intentions and objectives
 
 + LUYA is not a one-click installation product like WordPress and others.
 + Configuration data is stored in versioned files (not in the database).
-+ DRY concept
++ We adhere to the DRY ("Don't repeat yourself") concept.
 + System code belongs into the vendor directory.
 
 ## 3. Code of conduct
 
-+ Always benevolent, no matter what question is posed.
++ We are always benevolent, no matter what question.
 + No one will be embarrassed, no one knows it all.
-+ We are good role models. No swearwords. No Discrimination.
++ We are good role models. No swearwords. No discrimination.
 + Communication is in English.
 
-## 4. Becoming a member
+## 4. Requirements for becoming a member
 
 + Intention for a long-term contribution
 + Must have commits
 + Pull requests must be of high quality
 
 ## 5. Members
 
-Current LUYA Organisation Members with the respective role:
-
 |Github|Name|Role
 |------|----|----
 |[nadar](https://github.com/nadar)|Basil Suter|Project Lead
@@ -41,20 +39,20 @@ Current LUYA Organisation Members with the respective role:
 
 |Role|Description|Planning/Strategy|Reaction** within 48h|Voting|Commit Access/PR
 |-----|------------|----------------|--------------|------|----------------
-|Project Lead|Core member inclusive Planning and Strategy Function|Yes|Yes|Yes|Yes
-|Core Member|Can commit and merge PR, must react within 48h to PR, mention, assignments|No|Yes|Yes|Yes
+|Project Lead|Core member, including planning and strategy tasks|Yes|Yes|Yes|Yes
+|Core Member|Can commit and merge pull requests, must react within 48 to pull requests, mentions, assignments|No|Yes|Yes|Yes
 |Maintainer|Can comment, assign and set labels but can not write into the repos.|No|No|Yes|No
 |Contributor|Allows to invite members to the team without long-term obligations but still with a sense of being part of the project.|No|No|No|No
 |Extension Manager|Has commit access to specific extensions and has to react as far as these are concerned|No|Yes*|Yes|Yes*
 
 \* Only for the given extensions.  
-\*\* Mentiones, comments, pull requests, assignements, issues, reviews
+\*\* Mentions, comments, pull requests, assignements, issues, reviews
 
-## 7) Rights and possibilities of the members
+## 7. Rights and possibilities of members
 
 + Voting required
   + Issue/pull request must have the label “requires decision” assigned.
-  + All members with allowed voting role (Project Lead, Core Member, Maintainer, Extension Manager) have 7 days time to vote after a issue/pull request was created with “requires decision” label.
+  + All members with allowed voting role (Project Lead, Core Member, Maintainer, Extension Manager) have 7 days time to vote after a issue/pull request was created with “requires decision” label.	+  + All members with the role XYZ have 7 days time to vote after a issue/pull request was created.
   + Long-term intentions and objectives may not be changed, see [Long-term intention and objectives](#2-long-term-intention-and-objectives).
 + No voting required
   + Use of the technology.