aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorAlex Gaynor <alex.gaynor@gmail.com>2013-12-21 19:37:24 -0800
committerAlex Gaynor <alex.gaynor@gmail.com>2013-12-21 19:37:24 -0800
commit95243f5b34f6cdfc16fb95669efbe2a61ac81179 (patch)
treed4dadb815951ea365e83df154b0b980364b1ac86 /docs
parent15cf6b995624e938209e611f3953dd8dbb7a57b8 (diff)
downloadcryptography-95243f5b34f6cdfc16fb95669efbe2a61ac81179.tar.gz
cryptography-95243f5b34f6cdfc16fb95669efbe2a61ac81179.tar.bz2
cryptography-95243f5b34f6cdfc16fb95669efbe2a61ac81179.zip
English, how does it work?
Diffstat (limited to 'docs')
-rw-r--r--docs/contributing.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/contributing.rst b/docs/contributing.rst
index f176393f..b1702df8 100644
--- a/docs/contributing.rst
+++ b/docs/contributing.rst
@@ -53,7 +53,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 it's results are almost
+is that secure code looks just like insecure code, and its results are almost
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 which should be both followed, and should inspire other API choices: