diff options
author | Alex Gaynor <alex.gaynor@gmail.com> | 2015-09-24 21:48:51 -0400 |
---|---|---|
committer | Alex Gaynor <alex.gaynor@gmail.com> | 2015-09-24 21:48:51 -0400 |
commit | 16b67fce20f79ce326194e88156bd3e734730362 (patch) | |
tree | d2368258ff4bf32ef8c074430eda8b6f9c5e434d /docs/development/submitting-patches.rst | |
parent | 8208fe6a9b92bc7e7060448d75d1641bda62fc8a (diff) | |
download | cryptography-16b67fce20f79ce326194e88156bd3e734730362.tar.gz cryptography-16b67fce20f79ce326194e88156bd3e734730362.tar.bz2 cryptography-16b67fce20f79ce326194e88156bd3e734730362.zip |
some commas that look correct
Diffstat (limited to 'docs/development/submitting-patches.rst')
-rw-r--r-- | docs/development/submitting-patches.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/development/submitting-patches.rst b/docs/development/submitting-patches.rst index 66105843..33cde101 100644 --- a/docs/development/submitting-patches.rst +++ b/docs/development/submitting-patches.rst @@ -48,7 +48,7 @@ API considerations Most projects' APIs are designed with a philosophy of "make easy things easy, and make hard things possible". One of the perils of writing cryptographic code is that secure code looks just like insecure code, and its results are almost -always indistinguishable. As a result ``cryptography`` has, as a design +always indistinguishable. As a result, ``cryptography`` has, as a design philosophy: "make it hard to do insecure things". Here are a few strategies for API design that should be both followed, and should inspire other API choices: |