X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=CONTRIBUTING;h=0f11362492934156d13211e14acd16de1b56de0e;hp=d826e8805f5542b06f146cbdf34758d0bfc4394f;hb=8cc44d970ced1004db0727d7a7b3e2709c442e55;hpb=75737d4fcd19974dc7b21fa790836435dafb294c

diff --git a/CONTRIBUTING b/CONTRIBUTING
index d826e8805f..0f11362492 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -57,15 +57,19 @@ the acceptance and review process faster:
 
     3.  Patches should be as current as possible.  When using GitHub, please
     expect to have to rebase and update often. Note that we do not accept merge
-    commits, so please avoid these in any pull request. You will be asked to
-    remove them before a patch is considered acceptable.
+    commits. You will be asked to remove them before a patch is considered
+    acceptable.
 
     4.  Patches should follow our coding style (see
     https://www.openssl.org/policies/codingstyle.html) and compile without
-    warnings. Where gcc or clang is availble you should use the
+    warnings. Where gcc or clang is available you should use the
     --strict-warnings Configure option.  OpenSSL compiles on many varied
     platforms: try to ensure you only use portable features.
 
     5.  When at all possible, patches should include tests. These can either be
     added to an existing test, or completely new.  Please see test/README
     for information on the test framework.
+
+    6.  New features or changed functionality must include documentation. Please
+    look at the "pod" files in doc/apps, doc/crypto and doc/ssl for examples of
+    our style.