DOC: Avoid using "set of" when talking about an ordered list.

... or when the input isn't/cannot be a set.  I left a few usages, e.g.
in random sampling, where "set" is reasonable as informal description of
an array as the order doesn't matter; however, for e.g. np.gradient the
order of the returned list is clearly important, so "set" is wrong.

Also some other minor doc edits noticed during the grepping: using
`shape` instead of `form` in `cov` is consistent with most other places;
the wording in `Polynomial.trim` now matches other methods on the same
class.

2 files changed, 3 insertions, 3 deletions

diff --git a/benchmarks/benchmarks/bench_app.py b/benchmarks/benchmarks/bench_app.py
index bee95c201..d22aa2e09 100644
--- a/benchmarks/benchmarks/bench_app.py
+++ b/benchmarks/benchmarks/bench_app.py
@@ -70,8 +70,8 @@ class MaxesOfDots(Benchmark):
 
         Arrays must agree only on the first dimension.
 
-        For numpy it a join benchmark of dot products and max()
-        on a set of arrays.
+        Numpy uses this as a simultaneous benchmark of 1) dot products
+        and 2) max(<array>, axis=<int>).
         """
         feature_scores = ([0] * len(arrays))
         for (i, sd) in enumerate(arrays):
diff --git a/benchmarks/benchmarks/common.py b/benchmarks/benchmarks/common.py
index b65cc5fd2..b95d09192 100644
--- a/benchmarks/benchmarks/common.py
+++ b/benchmarks/benchmarks/common.py
@@ -14,7 +14,7 @@ nx, ny = 1000, 1000
 # time-consuming functions (ufunc, linalg, etc)
 nxs, nys = 100, 100
 
-# a set of interesting types to test
+# a list of interesting types to test
 TYPES1 = [
     'int16', 'float16',
     'int32', 'float32',