Fix typos (#372)

Crozzers · web-flow · commit b29378679884 · 2021-02-17T21:36:09.000+01:00
* Fixed some typos

* More spell checking with aspell
diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
@@ -30,6 +30,7 @@ Code
 
 Docs
 ----
+  * [Crozzers](https://github.com/Crozzers)
   * [EJEP](https://github.com/EJEP)
   * [Franzqat](https://github.com/franzqat)
   * [Harmon758](https://github.com/Harmon758)
diff --git a/pyowm/agroapi10/search.py b/pyowm/agroapi10/search.py
@@ -180,7 +180,7 @@ def with_img_type(self, image_type):
 
     def with_preset(self, preset):
         """
-        Returns the seach results having the specified preset
+        Returns the search results having the specified preset
 
         :param preset: the desired image preset (valid values are provided by the
             `pyowm.agroapi10.enums.PresetEnum` enum)
diff --git a/pyowm/commons/tile.py b/pyowm/commons/tile.py
@@ -92,7 +92,7 @@ def geoocoords_to_tile_coords(cls, lon, lat, zoom):
     @classmethod
     def tile_coords_to_bbox(cls, x, y, zoom):
         """
-        Calculates the lon/lat estrema of the bounding box corresponding to specific tile coordinates. Output coodinates
+        Calculates the lon/lat estrema of the bounding box corresponding to specific tile coordinates. Output coordinates
         are in degrees and in the Mercator Projection (http://en.wikipedia.org/wiki/Mercator_projection)
 
         :param x: the x tile coordinates
diff --git a/pyowm/utils/formatting.py b/pyowm/utils/formatting.py
@@ -134,7 +134,7 @@ def to_UNIXtime(timeobject):
 def ISO8601_to_UNIXtime(iso):
     """
     Converts an ISO8601-formatted string in the format
-    ``YYYY-MM-DD HH:MM:SS+00:00`` to the correspondant UNIXtime
+    ``YYYY-MM-DD HH:MM:SS+00:00`` to the correspondent UNIXtime
 
     :param iso: the ISO8601-formatted string
     :type iso: string
diff --git a/pyowm/weatherapi25/historian.py b/pyowm/weatherapi25/historian.py
@@ -92,7 +92,7 @@ def wind_series(self):
 
     def max_temperature(self,  unit='kelvin'):
         """Returns a tuple containing the max value in the temperature
-        series preceeded by its timestamp
+        series preceded by its timestamp
         
         :param unit: the unit of measure for the temperature values. May be
             among: '*kelvin*' (default), '*celsius*' or '*fahrenheit*'
@@ -114,7 +114,7 @@ def max_temperature(self,  unit='kelvin'):
         
     def min_temperature(self, unit='kelvin'):
         """Returns a tuple containing the min value in the temperature
-        series preceeded by its timestamp
+        series preceded by its timestamp
         
         :param unit: the unit of measure for the temperature values. May be
             among: '*kelvin*' (default), '*celsius*' or '*fahrenheit*'
@@ -157,7 +157,7 @@ def average_temperature(self, unit='kelvin'):
     
     def max_humidity(self):
         """Returns a tuple containing the max value in the humidity
-        series preceeded by its timestamp
+        series preceded by its timestamp
 
         :returns: a tuple
         :raises: ValueError when the measurement series is empty
@@ -167,7 +167,7 @@ def max_humidity(self):
         
     def min_humidity(self):
         """Returns a tuple containing the min value in the humidity
-        series preceeded by its timestamp
+        series preceded by its timestamp
 
         :returns: a tuple
         :raises: ValueError when the measurement series is empty
@@ -186,7 +186,7 @@ def average_humidity(self):
 
     def max_pressure(self):
         """Returns a tuple containing the max value in the pressure
-        series preceeded by its timestamp
+        series preceded by its timestamp
 
         :returns: a tuple
         :raises: ValueError when the measurement series is empty
@@ -196,7 +196,7 @@ def max_pressure(self):
         
     def min_pressure(self):
         """Returns a tuple containing the min value in the pressure
-        series preceeded by its timestamp
+        series preceded by its timestamp
 
         :returns: a tuple
         :raises: ValueError when the measurement series is empty
@@ -215,7 +215,7 @@ def average_pressure(self):
 
     def max_rain(self):
         """Returns a tuple containing the max value in the rain
-        series preceeded by its timestamp
+        series preceded by its timestamp
 
         :returns: a tuple
         :raises: ValueError when the measurement series is empty
@@ -225,7 +225,7 @@ def max_rain(self):
         
     def min_rain(self):
         """Returns a tuple containing the min value in the rain
-        series preceeded by its timestamp
+        series preceded by its timestamp
 
         :returns: a tuple
         :raises: ValueError when the measurement series is empty
diff --git a/sphinx/contributing.md b/sphinx/contributing.md
@@ -1,14 +1,14 @@
 # Contributing
 
-Contributing is easy anwd welcome
+Contributing is easy and welcome
  
 You can contribute to PyOWM in a lot of ways:
 
   - reporting a reproducible defect (eg. bug, installation crash, ...)
   - make a wish for a reasonable new feature
   - increase the test coverage
   - refactor the code
-  - improve PyOWM reach on platforms (eg. bundle it for Linux distros, managers, oding, testing, packaging, reporting issues) are welcome!
+  - improve PyOWM reach on platforms (eg. bundle it for Linux distros, managers, coding, testing, packaging, reporting issues) are welcome!
   
 And last but not least... use it! Use PyOWM in your own projects, as [lots of people already do](https://github.com/csparpa/pyowm/wiki/Community-Projects-using-PyOWM).
 
@@ -26,9 +26,9 @@ That's simple: what you need to do is just open a new issue on GitHub.
 
 ## Bug reports - general principles
 In order to allow the community to understand what the bug is, *you should provide as much information as possible* on it.
-Vague or succint bug reports are not useful and will very likely result in follow ups needed.
+Vague or succinct bug reports are not useful and will very likely result in follow ups needed.
 
-*Only bugs related to PyOWM will be addressed*: it might be that you're using PyOWM in a broader context (eg. a webapplication)
+*Only bugs related to PyOWM will be addressed*: it might be that you're using PyOWM in a broader context (eg. a web application)
 so bugs affecting the broader context are out of scope - unless they are caused in chain to PyOWM issues.
 
 Also, please do understand that we can only act on *reproducible bugs*: this means that a bug does not exist if it is
@@ -74,7 +74,7 @@ just run:
 
 `pip install -r dev-requirements.txt`
 
-It is adviced that you do it on a [virtualenv](https://virtualenv.pypa.io/en/stable/).
+It is advised that you do it on a [virtualenv](https://virtualenv.pypa.io/en/stable/).
 
 ## Guidelines for code branching
 Simple ones:
diff --git a/sphinx/index.rst b/sphinx/index.rst
@@ -239,7 +239,7 @@ If you already have PyOWM 2.x installed and want to upgrade to safely update it
     $ pip install --upgrade pyowm>=2.0,<3.0
 
 
-Get the lastest development version
+Get the latest development version
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 You can install the development trunk with _pip_:
diff --git a/sphinx/v3/agro-api-usage-examples.md b/sphinx/v3/agro-api-usage-examples.md
@@ -32,7 +32,7 @@ Read on to discover what you can do with it.
 
 A polygon represents an area on a map upon which you can issue data queries. Each polygon has a unique ID, an optional
 name and links back to unique OWM ID of the User that owns that polygon. Each polygon has an area that is expressed 
-in hacres, but you can also get it in squared kilometers:
+in acres, but you can also get it in squared kilometers:
 
 ```python
 pol                  # this is a pyowm.agro10.polygon.Polygon instance
@@ -133,7 +133,7 @@ Soil data is updated twice a day.
 
 This is the real meat in Agro API: the possibility to obtain **satellite imagery** right upon your polygons!
 
-### Overwiew
+### Overview
 
 Satellite Imagery comes in 3 formats:
   - **PNG images**
@@ -416,7 +416,7 @@ Currently only PNG and GEOTIFF imagery is available
 
 ### Supported color palettes
 Supported color palettes are provided by the `pyowm.agroapi10.enums.PaletteEnum` enumerator which returns strings,
-each one representing a color palette for NDVI imges:
+each one representing a color palette for NDVI images:
 
  ```python
 from pyowm.agroapi10.enums import PaletteEnum
diff --git a/sphinx/v3/air-pollution-api-usage-examples.md b/sphinx/v3/air-pollution-api-usage-examples.md
@@ -59,7 +59,7 @@ max_sample = coi.get_co_sample_with_highest_vmr()
 min_sample = coi.get_co_sample_with_lowest_vmr()
 ```
 
-If you want to know if a COIndex refers to the future - aka: is a forecast - wth respect to the
+If you want to know if a COIndex refers to the future - aka: is a forecast - with respect to the
 current timestamp, then use the `is_forecast()` method
 
 
@@ -119,9 +119,9 @@ oz.get_reference_time()
 oz.get_reception_time()
 ```
 
-If you want to know if an Ozone measurement refers to the future - aka: is a forecast - wth respect to the
+If you want to know if an Ozone measurement refers to the future - aka: is a forecast - with respect to the
 current timestamp, then use the `is_forecast()` method
 
 
 ### Querying Nitrogen dioxide (NO2) and Sulfur Dioxide (SO2) data
-This works exactly as for O2 adata - please refer to that bit of the docs
+This works exactly as for O2 data - please refer to that bit of the docs
diff --git a/sphinx/v3/alerts-api-usage-examples.md b/sphinx/v3/alerts-api-usage-examples.md
@@ -89,7 +89,7 @@ am.delete_alert_for(trigger, alert)
 This is the Alert API object model:
 
   - *Trigger*: collection of alerts to be met over specified areas and within a specified time frame according to specified weather params conditions
-  - *Condition*: rule for matching a weather measuerment with a specified threshold
+  - *Condition*: rule for matching a weather measurement with a specified threshold
   - *Alert*: whenever a condition is met, an alert is created (or updated) and can be polled to verify when it has been met and what the actual weather param value was.
   - *Area*: geographic area over which the trigger is checked
   - *AlertChannel*: as OWM plans to add push-oriented alert channels (eg. push notifications), we need to encapsulate this into a specific class
@@ -283,8 +283,8 @@ A Trigger is the local proxy for the corresponding entry on the OWM API: Trigger
 `pyowm.alertapi30.alertmanager.AlertManager` instances.
 
 Each Trigger has these attributes:
-  - start_after_millis: _with resepect to the time when the trigger will be crated on the Alert API_, how many milliseconds after should it begin to be checked for conditions matching
-  - end_after_millis: _with resepect to the time when the trigger will be crated on the Alert API_, how many milliseconds after should it end to be checked for conditions matching
+  - start_after_millis: _with respect to the time when the trigger will be created on the Alert API_, how many milliseconds after should it begin to be checked for conditions matching
+  - end_after_millis: _with respect to the time when the trigger will be created on the Alert API_, how many milliseconds after should it end to be checked for conditions matching
   - alerts: a list of `pyowm.alertapi30.alert.Alert` instances, which are the alerts that the trigger has fired so far
   - conditions: a list of `pyowm.alertapi30.condition.Condition` instances
   - area: a list of `pyowm.utils.geo.Geometry` instances, representing the geographic area on which the trigger's conditions need to be checked
diff --git a/sphinx/v3/city-id-registry-examples.md b/sphinx/v3/city-id-registry-examples.md
@@ -2,6 +2,6 @@
 
 Using city IDS instead of toponyms or geographic coordinates is the preferred way of querying the OWM weather API
  
-You can obtain the city ID for your toponyms/geoocoords of interest via the `City ID Registry`.
+You can obtain the city ID for your toponyms/geocoords of interest via the `City ID Registry`.
 
 Please refer to the `Code Recipes` page, section: `Identifying cities and places via city IDs`, to get info about it
diff --git a/sphinx/v3/code-recipes.md b/sphinx/v3/code-recipes.md
@@ -148,7 +148,7 @@ city_id_registry = owm.city_id_registry()
 ```
 
 #### Get the ID of a city given its name
-Don't forget that there is a high probabilty that your city is not unique in the world, and multiple cities with the same name exist in other countries
+Don't forget that there is a high probability that your city is not unique in the world, and multiple cities with the same name exist in other countries
 Therefore specify toponyms and country 2-letter names separated by comma. Eg: if you search for the British `London` you'll likely multiple results: 
 you then should also specify the country (`GB`) to narrow the search only to Great Britain.
 
@@ -225,7 +225,7 @@ Simply put:
 Both geocoding actions are performed via a `geocoding_manager` object and will require an actual call to be made to the
 OWM API: so please bear that in mind because that will count against your amount of allowed API calls
 
-#### Direct gecocoding of a toponym
+#### Direct geocoding of a toponym
 
 The call is very similar to `ids_for` and `locations_for`.
 
@@ -255,7 +255,7 @@ list_of_locations = mgr.geocode('London', country='GB', limit=3)
 list_of_locations = mgr.geocode('London', country='US', state_code='OH')
 ```
 
-#### Reverse gecocoding of geocoordinates
+#### Reverse geocoding of geocoordinates
 With reverse geocoding you input a lat/lon float couple and retrieve a list all the `Location` objects associated with 
 these coordinates.
 
@@ -345,7 +345,7 @@ one_call = mgr.one_call(lat=52.5244, lon=13.4105, exclude='minutely,hourly', uni
 # the various units for the different options are shown here: https://openweathermap.org/weather-data
 one_call.current.temperature() # Eg.: 74.07 (deg F)
 
-# the example above does not retrieve minutely or hourly data, so it will not be availabe in the one_call object
+# the example above does not retrieve minutely or hourly data, so it will not be available in the one_call object
 # available exclude options are defined by the One Call API
 # BUT using 'current' will error, as the pyowm one_call requires it
 # as of 2020.08.07 available values are: 'minutely', 'hourly', 'daily'
diff --git a/sphinx/v3/faq.md b/sphinx/v3/faq.md
@@ -30,7 +30,7 @@ As stated in the documentation home page, OpenWeatherMap API recently "blocked"
 
 This means that PyOWM might return authorization errors in that case.
 
-This behaviour is not showing if you use API keys issued time ago - unfortunately I have no wasy to be more precise as OWM never stated this officially.
+This behaviour is not showing if you use API keys issued time ago - unfortunately I have no way to be more precise as OWM never stated this officially.
 
 **The proper way to obtain the data you are looking for is to call the "OneCall" PyOWM methods using your API key**
 
diff --git a/sphinx/v3/global-pyowm-usage-examples.md b/sphinx/v3/global-pyowm-usage-examples.md
@@ -18,7 +18,7 @@ weather = mgr.weather_at_place('London,GB').weather  # get the weather at London
 dump_dict = weather.to_dict()
 ```
 
-This is useful as you can save the dump dictionaries to files (eg. using Pyhon `json` or `pickle` modules)
+This is useful as you can save the dump dictionaries to files (eg. using Python `json` or `pickle` modules)
 
 ## Printing objects
 Most of PyOWM objects can be pretty-printed for a quick introspection:
diff --git a/sphinx/v3/stations-api-usage-examples.md b/sphinx/v3/stations-api-usage-examples.md
@@ -46,7 +46,7 @@ datapoints that you query against the API come in the form of:
  `stationsapi30.measurement.AggregatedMeasurement` objects.
 
 
-Each `stationsapi30.measurement.Measurement` cointains a reference to the
+Each `stationsapi30.measurement.Measurement` contains a reference to the
 `Station` it belongs to:
 
 ```python
