Browse Source

[3109] Re-justify paragraph (after changes in previous commits)

Mukund Sivaraman 11 years ago
parent
commit
d640e2711d
1 changed files with 8 additions and 8 deletions
  1. 8 8
      doc/devel/contribute.dox

+ 8 - 8
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
 process much easier if it is for latest code from the Git \c master
 branch.
 branch.
 
 
-Ok, so you have written a patch? Great! Before you submit it, make sure that
+Ok, so you have written a patch? Great! Before you submit it, make sure
-your code compiles. This may seem obvious, but there's more to
+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
+it. You have surely checked that it compiles on your system, but BIND10
-BIND10 is portable software. Besides Linux, it is compiled and used on
+is portable software. Besides Linux, it is compiled and used on
-relatively uncommon systems like OpenBSD and Solaris 11. Will your
+relatively uncommon systems like OpenBSD and Solaris 11. Will your code
-code compile and work there? What about endianess? It is likely
+compile and work there? What about endianess? It is likely that you used
-that you used a regular x86 architecture machine to write your patch, but the software is expected to run on many
+a regular x86 architecture machine to write your patch, but the software
-other architectures.
+is expected to run on many other architectures.
 
 
 Does your patch conforms to BIND10
 Does your patch conforms to BIND10
 http://bind10.isc.org/wiki/CodingGuidelines? You still can submit
 http://bind10.isc.org/wiki/CodingGuidelines? You still can submit