docs: minor grammar fixes

README.md

@@ -220,11 +220,11 @@ should be aware of before submitting a pull request:
 
 * Only requests that have passing CI builds (Travis) will be merged.
 * Code is checked with `flakes8` and `pydocstyle` during build so this
-  implicitely means that compliance with PEP-8 and PEP-257 are mandatory.
+  implicitly means that compliance with PEP-8 and PEP-257 is mandatory.
 * No changes that decrease coverage will be merged.
 
 One thing: if you submit a PR please do not rebase it later unless you
-are asked for that explicitely. Reviewing pull requests that suddenly had 
+are asked for that explicitly. Reviewing pull requests that suddenly had
 their history rewritten just drives me crazy.
 
 

docs/guide/parameters.rst

@@ -284,7 +284,7 @@ user to search for data in region defined as a polygon. Polygon can be simply
 represented by just an ordered list of points. But does it makes sense
 to define your polygon as ``point`` parameter with ``many=True``? Probably not.
 In case where order of data is important you need some custom parameter class
-that will explicitely define how to handle such parameters. The naive
+that will explicitly define how to handle such parameters. The naive
 implementation for polygon parameter could be as follows:
 The naive
 

src/graceful/resources/base.py

@@ -66,7 +66,7 @@ def __new__(mcs, name, bases, namespace, **kwargs):
         namespace[mcs._params_storage_key] = mcs._get_params(bases, namespace)
         return super().__new__(
             # note: there is no need preserve order in namespace anymore so
-            # we convert it explicitely to dict
+            # we convert it explicitly to dict
             mcs, name, bases, dict(namespace),
         )
 
@@ -76,7 +76,7 @@ def __init__(cls, name, bases, namespace, **kwargs):
 
         try:
             # note: attribute is stored only if with_context keyword
-            #       argument is not specified explicitely. This way
+            #       argument is not specified explicitly. This way
             #       we are able to guess if proper warning need to be
             #       displayed to the user.
             # future: remove in 1.x

src/graceful/serializers.py

@@ -59,7 +59,7 @@ def __new__(mcs, name, bases, namespace):
         namespace[mcs._fields_storage_key] = mcs._get_fields(bases, namespace)
         return super().__new__(
             # note: there is no need preserve order in namespace anymore so
-            # we convert it explicitely to dict
+            # we convert it explicitly to dict
             mcs, name, bases, dict(namespace)
         )
 
@@ -157,7 +157,7 @@ def from_representation(self, representation):
                 continue
 
             try:
-                # if field has explicitely specified source then use it
+                # if field has explicitly specified source then use it
                 # else fallback to field name.
                 # Note: field does not know its name
                 object_dict[field.source or name] = field.from_representation(