From 53ac7830cb501834fee9dda0c081261c1b62997c Mon Sep 17 00:00:00 2001
From: Paul Sokolovsky <pfalcon@users.sourceforge.net>
Date: Fri, 15 Apr 2016 20:08:51 +0300
Subject: [PATCH] docs/speed_python: Add article.

---
 docs/reference/speed_python.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reference/speed_python.rst b/docs/reference/speed_python.rst
index 7bc486805..2f1d16cea 100644
--- a/docs/reference/speed_python.rst
+++ b/docs/reference/speed_python.rst
@@ -99,7 +99,7 @@ of slice it points too.
 
 A ``memoryview`` can only be applied to objects supporting the buffer protocol - this
 includes arrays but not lists. Small caveat is that while memoryview object is live,
-it also keeps alive the original buffer object. So, memoryviews isn't universal
+it also keeps alive the original buffer object. So, a memoryview isn't a universal
 panacea. For instance, in the example above, if you are done with 10K buffer and
 just need those bytes 30:2000 from it, it may be better to make a slice, and let
 the 10K buffer go (be ready for garbage collection), instead of making a
-- 
GitLab