Fix typos in style/naming and functions-and-methods

Author: alxgnon

features/functions-and-methods/convenience.md

@@ -35,7 +35,7 @@ coherent sets of convenience methods that are easy to remember:
 * _Coherent_: Look for small groups of convenience methods that make sense to
   include together. For example, the `Path` API mentioned above includes a small
   selection of the most common filesystem operations that take a `Path`
-  argument.  If one convenience method strongly suggests the existence others,
+  argument.  If one convenience method strongly suggests the existence of others,
   consider adding the whole group.
 * _Memorable_: It is not worth saving a few characters of typing if you have to
   look up the name of a convenience method every time you use it. Add

style/naming.md

@@ -126,7 +126,7 @@ Iterators require introducing and exporting new types. These types should use
 the following naming convention:
 
 * **Base name**. If the iterator yields something that can be described with a
-   specific noun, the base name shoudl be the pluralization of that noun
+   specific noun, the base name should be the pluralization of that noun
    (e.g. an iterator yielding words is called `Words`). Generic contains use the
    base name `Items`.