From 0c11d0427e12557fa41cdfbc00f6a83a36c58af7 Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Thu, 2 Jun 2016 22:24:22 -0700 Subject: Random grammar stuff (#2955) --- docs/development/getting-started.rst | 2 +- docs/development/submitting-patches.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/development/getting-started.rst b/docs/development/getting-started.rst index 0bbb18ce..3ad9fe82 100644 --- a/docs/development/getting-started.rst +++ b/docs/development/getting-started.rst @@ -27,7 +27,7 @@ You must have installed `OpenSSL`_ via `Homebrew`_ or `MacPorts`_ and must set ``CFLAGS`` and ``LDFLAGS`` environment variables before installing the ``dev-requirements.txt`` otherwise pip will fail with include errors. -For example with `Homebrew`_: +For example, with `Homebrew`_: .. code-block:: console diff --git a/docs/development/submitting-patches.rst b/docs/development/submitting-patches.rst index 563bc81f..475e7037 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: -- cgit v1.2.3