diff --git a/doc/devel/contribute.dox b/doc/devel/contribute.dox
index 2251885ca5..0d57974882 100644
--- a/doc/devel/contribute.dox
+++ b/doc/devel/contribute.dox
@@ -44,14 +44,14 @@ provide a patch against the latest stable release, it makes the review
 process much easier if it is for latest code from the Git \c master
 branch.
 
-Ok, so you have written a patch? Great! Before you submit it, make sure that
-your code compiles. This may seem obvious, but there's more to
-it. You have surely checked that it compiles on your system, but
-BIND10 is portable software. Besides Linux, it is compiled and used on
-relatively uncommon systems like OpenBSD and Solaris 11. Will your
-code compile and work there? What about endianess? It is likely
-that you used a regular x86 architecture machine to write your patch, but the software is expected to run on many
-other architectures.
+Ok, so you have written a patch? Great! Before you submit it, make sure
+that your code compiles. This may seem obvious, but there's more to
+it. You have surely checked that it compiles on your system, but BIND10
+is portable software. Besides Linux, it is compiled and used on
+relatively uncommon systems like OpenBSD and Solaris 11. Will your code
+compile and work there? What about endianess? It is likely that you used
+a regular x86 architecture machine to write your patch, but the software
+is expected to run on many other architectures.
 
 Does your patch conforms to BIND10
 http://bind10.isc.org/wiki/CodingGuidelines? You still can submit