summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorThomas A Caswell <tcaswell@gmail.com>2019-07-23 18:59:03 -0400
committerGitHub <noreply@github.com>2019-07-23 18:59:03 -0400
commitdf68d9bf481cfb2f297010cc1e1c379006549a96 (patch)
treee5be8d0f18f2b3c43736cacc7ec2dc8009071101 /doc
parent423c79c67250fff01f38cdf4138c80d4e540f08f (diff)
downloadnumpy-df68d9bf481cfb2f297010cc1e1c379006549a96.tar.gz
DOC: Apply wording changes from @mdhaber
Co-Authored-By: Matt Haberland <mdhaber@mit.edu>
Diffstat (limited to 'doc')
-rw-r--r--doc/neps/nep-0028-deprecation_policy.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/neps/nep-0028-deprecation_policy.rst b/doc/neps/nep-0028-deprecation_policy.rst
index f0b35c45e..cde748a32 100644
--- a/doc/neps/nep-0028-deprecation_policy.rst
+++ b/doc/neps/nep-0028-deprecation_policy.rst
@@ -15,11 +15,11 @@ Abstract
All projects across the ecosystem should adopt a common time window
based policy for increasing the minimum version of CPython and NumPy
that downstream projects support. By standardizing this policy
-across community we will make it easier for down stream projects to
+across the community we will make it easier for downstream projects to
plan.
-This is an unusual NEP in that it is recommendations for community
-wide policy and not for changes to NumPy itself. However, we do not
+This is an unusual NEP in that it is recommendations for community-wide
+policy and not for changes to NumPy itself. However, we do not
currently have a place for SPEEPs (Scientific Python Ecosystem
Enhancement Proposals) and given NumPy's central role in our community
this seems like the proper place to document this.