1 files changed, 4 insertions, 4 deletions

diff --git a/documentation/content/en/articles/rc-scripting/_index.adoc b/documentation/content/en/articles/rc-scripting/_index.adoc
index ae68c31c28..cdfa656e53 100644
--- a/documentation/content/en/articles/rc-scripting/_index.adoc
+++ b/documentation/content/en/articles/rc-scripting/_index.adoc
@@ -92,7 +92,7 @@ Finally, an important part of the [.filename]#rc.d# framework is man:rcorder[8],
 It can help [.filename]#/etc/rc.shutdown#, too, because the proper order for the shutdown sequence is opposite to that of startup.
 
 The BSD [.filename]#rc.d# design is described in <<lukem, the original article by Luke Mewburn>>, and the [.filename]#rc.d# components are documented in great detail in <<manpages, the respective manual pages>>.
-However, it might not appear obvious to an [.filename]#rc.d# newbie how to tie the numerous bits and pieces together in order to create a well-styled script for a particular task.
+However, it might not appear obvious to an [.filename]#rc.d# newbie how to tie the numerous bits and pieces together to create a well-styled script for a particular task.
 Therefore this article will try a different approach to describe [.filename]#rc.d#.
 It will show which features should be used in a number of typical cases, and why.
 Note that this is not a how-to document because our aim is not at giving ready-made recipes, but at showing a few easy entrances into the [.filename]#rc.d# realm.
@@ -100,7 +100,7 @@ Neither is this article a replacement for the relevant manual pages.
 Do not hesitate to refer to them for more formal and complete documentation while reading this article.
 
 There are prerequisites to understanding this article.
-First of all, you should be familiar with the man:sh[1] scripting language in order to master [.filename]#rc.d#.
+First of all, you should be familiar with the man:sh[1] scripting language to master [.filename]#rc.d#.
 In addition, you should know how the system performs userland startup and shutdown tasks, which is described in man:rc[8].
 
 This article focuses on the FreeBSD branch of [.filename]#rc.d#.
@@ -110,7 +110,7 @@ Nevertheless, it may be useful to NetBSD developers, too, because the two branch
 == Outlining the task
 
 A little consideration before starting `$EDITOR` will not hurt.
-In order to write a well-tempered [.filename]#rc.d# script for a system service, we should be able to answer the following questions first:
+To write a well-tempered [.filename]#rc.d# script for a system service, we should be able to answer the following questions first:
 
 * Is the service mandatory or optional?
 * Will the script serve a single program, e.g., a daemon, or perform more complex actions?
@@ -157,7 +157,7 @@ For example, a system admin can run our script manually, from the command line:
 
 [NOTE]
 ====
-In order to be properly managed by the [.filename]#rc.d# framework, its scripts need to be written in the man:sh[1] language.
+To be properly managed by the [.filename]#rc.d# framework, its scripts need to be written in the man:sh[1] language.
 If you have a service or port that uses a binary control utility or a startup routine written in another language, install that element in [.filename]#/usr/sbin# (for the system) or [.filename]#/usr/local/sbin# (for ports) and call it from a man:sh[1] script in the appropriate [.filename]#rc.d# directory.
 ====