[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  90ae68e0163b5cea806ea1f4e9a55be0207b8a2c (commit)
      from  73c14ab2b0f527f40d84b2957ec3df20394c7864 (commit)


- Log -----------------------------------------------------------------
commit 90ae68e0163b5cea806ea1f4e9a55be0207b8a2c
Author: Rich Salz <rsalz at akamai.com>
Date:   Wed Jan 14 16:13:08 2015 -0500

    Fix two typo's

-----------------------------------------------------------------------

Summary of changes:
 about/codingstyle.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/about/codingstyle.txt b/about/codingstyle.txt
index 0ffeedd..d133709 100644
--- a/about/codingstyle.txt
+++ b/about/codingstyle.txt
@@ -263,7 +263,7 @@ should be defined in a local header file that is not exported.
 
 Ideally, functions should be short and sweet, and do just one thing.
 A rule of thumb is that they should fit on one or two screenfuls of text
-as we all know), and do one thing and do that well.
+(25 lines as we all know), and do one thing and do that well.
 
 The maximum length of a function is often inversely proportional to the
 complexity and indentation level of that function. So, if you have a
@@ -449,7 +449,7 @@ Other API's use the following pattern:
     >= 1: success, with value returning additional information
     <= 0: failure with return value indicating why things failed
 
-Somtimes a return value of -1 can mean "should retry" (e.g., BIO, SSL, et al).
+Sometimes a return value of -1 can mean "should retry" (e.g., BIO, SSL, et al).
 
 Functions whose return value is the actual result of a computation,
 rather than an indication of whether the computation succeeded, are not