1 files changed, 4 insertions, 4 deletions

diff --git a/documentation/content/en/articles/explaining-bsd/_index.adoc b/documentation/content/en/articles/explaining-bsd/_index.adoc
index b188f0a2b0..ca7b1c02e5 100644
--- a/documentation/content/en/articles/explaining-bsd/_index.adoc
+++ b/documentation/content/en/articles/explaining-bsd/_index.adoc
@@ -145,8 +145,8 @@ Users can obtain a complete copy of any version.
 A large number of developers worldwide contribute to improvements to BSD.
 They are divided into three kinds:
 
-* _Contributors_ write code or documentation. They are not permitted to commit (add code) directly to the source tree. In order for their code to be included in the system, it must be reviewed and checked in by a registered developer, known as a __committer__.
-* _Committers_ are developers with write access to the source tree. In order to become a committer, an individual must show ability in the area in which they are active.
+* _Contributors_ write code or documentation. They are not permitted to commit (add code) directly to the source tree. For their code to be included in the system, it must be reviewed and checked in by a registered developer, known as a __committer__.
+* _Committers_ are developers with write access to the source tree. To become a committer, an individual must show ability in the area in which they are active.
 +
 It is at the individual committer's discretion whether they should obtain authority before committing changes to the source tree.
 In general, an experienced committer may make changes which are obviously correct without obtaining consensus.
@@ -154,7 +154,7 @@ For example, a documentation project committer may correct typographical or gram
 On the other hand, developers making far-reaching or complicated changes are expected to submit their changes for review before committing them
 In extreme cases, a core team member with a function such as Principal Architect may order that changes be removed from the tree, a process known as _backing out_.
 All committers receive mail describing each individual commit, so it is not possible to commit secretly.
-* The _Core team_. FreeBSD and NetBSD each have a core team which manages the project. The core teams developed in the course of the projects, and their role is not always well-defined. It is not necessary to be a developer in order to be a core team member, though it is normal. The rules for the core team vary from one project to the other, but in general they have more say in the direction of the project than non-core team members have.
+* The _Core team_. FreeBSD and NetBSD each have a core team which manages the project. The core teams developed in the course of the projects, and their role is not always well-defined. It is not necessary to be a developer to be a core team member, though it is normal. The rules for the core team vary from one project to the other, but in general they have more say in the direction of the project than non-core team members have.
 
 This arrangement differs from Linux in a number of ways:
 
@@ -206,7 +206,7 @@ This is particularly attractive for embedded applications.
 === What else should I know?
 
 Since fewer applications are available for BSD than Linux, the BSD developers created a Linux compatibility package, which allows Linux programs to run under BSD.
-The package includes both kernel modifications, in order to correctly perform Linux system calls, and Linux compatibility files such as the C library.
+The package includes both kernel modifications, to correctly perform Linux system calls, and Linux compatibility files such as the C library.
 There is no noticeable difference in execution speed between a Linux application running on a Linux machine and a Linux application running on a BSD machine of the same speed.
 
 The "all from one supplier" nature of BSD means that upgrades are much easier to handle than is frequently the case with Linux.