minor fixes for typos in doc (#286)

* minor fixes for typos  in doc

* changes sphinx version

* set sphinx

---------

Co-authored-by: Matthew Iannucci <[email protected]>

Author: fabricebrito

docs/source/ecosystem/index.md

@@ -4,7 +4,7 @@ Xpublish's ecosystem is made up of plugins and servers, and the folks who build
 
 ## Connect
 
-We have two main venues for discussing Xpublish and it's ecosystem, Github Discussions and Slack.
+We have two main venues for discussing Xpublish and its ecosystem, Github Discussions and Slack.
 
 ### Github Discussions
 

docs/source/getting-started/tutorial/index.md

@@ -1,6 +1,6 @@
 # Tutorial
 
-The Xpublish tutorial is designed for an experienced Xarray user (but not a server administrator) to be able to start at the beginning and build layers of understanding of how Xpublish and it's ecosystem work together.
+The Xpublish tutorial is designed for an experienced Xarray user (but not a server administrator) to be able to start at the beginning and build layers of understanding of how Xpublish and its ecosystem work together.
 
 If you are interested in developing plugins or administering servers, you may want to jump ahead to [using plugins](./using-plugins.md) or look to [deployment](../../user-guide/deployment/index.md) in the user guide..
 

docs/source/getting-started/tutorial/using-plugins.md

@@ -4,7 +4,7 @@
 Plugins were released in [0.3.0](https://github.com/xpublish-community/xpublish/releases/tag/0.3.0).
 ```
 
-Much of the power of Xpublish comes from it's [ecosystem](../../ecosystem/index) of plugins, which can quickly extend Xpublish with new capabilities.
+Much of the power of Xpublish comes from its [ecosystem](../../ecosystem/index) of plugins, which can quickly extend Xpublish with new capabilities.
 
 ```{note}
 For more details of the plugin system see the [plugin user guide](../../user-guide/plugins.md)

docs/source/getting-started/why-xpublish.md

@@ -12,13 +12,13 @@ Xpublish does this by using Xarray datasets as the core data interchange format
 
 ## An extendable core
 
-`xpublish` (the library) on it's own is designed to be relatively small and lightweight. It mainly defines plugin extension points, based around the internal exchange of Xarray datasets. It also defines a standard way to configure plugins, and how to load them.
+`xpublish` (the library) on its own is designed to be relatively small and lightweight. It mainly defines plugin extension points, based around the internal exchange of Xarray datasets. It also defines a standard way to configure plugins, and how to load them.
 
 It additionally provides an Xarray dataset accessor that allows for quickly serving a dataset, and a nice introduction path for creating new dataset based routers.
 
 ## A collection of plugins
 
-Xpublish really starts coming into it's own with the plugin ecosystem.
+Xpublish really starts coming into its own with the plugin ecosystem.
 
 Because `xpublish` the library has a relatively small API surface, but depends on familiar Xarray datasets, it becomes much easier to quickly develop large classes of plugins. Additionally by keeping most of the internet and storage facing elements of Xpublish out of the `xpublish` library, plugins can develop independently and at their own rate.
 

docs/source/index.md

@@ -67,7 +67,7 @@ with useful background information and explanation.
 
 The reference guide contains a detailed description of the Xpublish API/
 The reference describes how the methods work and which parameters can be used.
-It assumes that you have an an understanding of the key concepts.
+It assumes that you have an understanding of the key concepts.
 ```
 
 ```{grid-item-card} Developer guide

docs/source/user-guide/plugins.md

@@ -149,7 +149,7 @@ When you install a plugin library, the library takes advantage of the
 [entry point system](https://setuptools.pypa.io/en/latest/userguide/entry_point.html).
 
 This allows {py:class}`xpublish.Rest` to automatically find and use plugins.
-It only does this if plugins **are not** provided as an keyword argument.
+It only does this if plugins **are not** provided as a keyword argument.
 
 {py:class}`xpublish.Rest` uses {py:func}`plugins.manage.load_default_plugins` to
 load plugins from entry points.