Fix documentation typos (#6)

pending
(Andrea Manzi) #1

Fix documentation typos (#6)

  • fix typos
diff --git a/source/api.rst b/source/api.rst
index 64b5a41..a4add55 100644
--- a/source/api.rst
+++ b/source/api.rst
@@ -5,11 +5,10 @@ API
 
 Most if not all operations can be performed using the Onedata API.
 
-The official documentation is: https://onedata.org/#/home/api.
+The official documentation is at https://onedata.org/#/home/api.
 
-.. important:: In order to be able to access the `Onedata APIs`, ian access
+.. important:: In order to be able to access the `Onedata APIs`, an access
    token is required. See below for instructions on how to generate one.
-   to generate an access token.
 
 Getting an API access token
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -40,7 +39,6 @@ more information.
 The following variables should be set:
 
 * ``OIDC_TOKEN``: OpenID Connect Access token.
-  for obtaining it.
 * ``ONEZONE_HOST``: name or IP of the Onezone host (to use Onezone API).
 * ``ONEPROVIDER_HOST``: name or IP of the Oneprovider host (to use Oneprovider API).
 
@@ -101,11 +99,11 @@ switch.
 Working with PID / Handle
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
-It's possible to mint a Permanent Identifier (PID) for a space or subdirectory
+It's possible to mint a Permanent Identifier (PID) for a space or a subdirectory
 of a space using a handle service (like Handle.net) that is registered in the
 Onezone (EGI DataHub).
 
-Once done accessing the PID using its URL will redirect to the Onedata share,
+Once done, accessing the PID using its URL will redirect to the Onedata share
 allowing to retrieve the files.
 
 Prerequisites: access to a Handle service registered in the Onezone.
diff --git a/source/clients.rst b/source/clients.rst
index 1afe917..a4ec47d 100644
--- a/source/clients.rst
+++ b/source/clients.rst
@@ -3,7 +3,7 @@
 Clients
 -------
 
-The Oneclient code and basic documentation is available on
+The Oneclient code and basic documentation are available on
 `GitHub <https://github.com/onedata/oneclient>`_.
 
 The official documentation is hosted on the
@@ -17,7 +17,7 @@ Using the web interface
 
    Selecting EGI to connect using EGI Check-in
 
-   Using EGI Check-in it's possible to connect with its institute credentials.
+   Using EGI Check-in it's possible to connect with your institute credentials.
 
 .. figure:: _static/datahub-welcome-screen.png
    :alt: EGI DataHub landing page
@@ -41,7 +41,7 @@ Using the web interface
    Information about spaces supported by a Oneprovider
 
    The data space can be managed (ie. uploading/downloading/managing files and
-   metadata, manging space access) using the web browser.
+   metadata, managing space access) using the web browser.
 
 .. _auth-token-using-web-interface:
 
@@ -56,7 +56,7 @@ Tokens have to be generated from the **EGI DataHub** (Onezone) interface.
 .. figure:: _static/datahub-space-token.png
    :alt: EGI DataHub token management
 
-   Managing acccess tokens from EGI DataHub
+   Managing access tokens from EGI DataHub
 
    The access tokens can be created and managed using the EGI DataHub web interface.
 
@@ -64,7 +64,7 @@ Installing and testing Oneclient in a docker container
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 A quick and simple solution for testing is to install the client on demand in a
-container for a support Operating System flavor (mainly various CentOS and Ubuntu
+container for a supported Operating System flavor (mainly various CentOS and Ubuntu
 releases).
 
 The following variables have to be exported in the container:
@@ -89,7 +89,7 @@ The following variables have to be exported in the container:
    root@81dbd7e84438 /]# ls /tmp/space
 
 Here the data is mounted in ``/tmp/space``, creating a file into it will push it
-to the Oneprovider and it will be accessible up in the web interface and from
+to the Oneprovider and it will be accessible in the web interface and from
 other providers supporting the space.
 
 For a real production usage it's preferable to use the Oneclient container as a
@@ -102,7 +102,7 @@ Docker containers for the Oneclient are available, the existing versions can be
 seen on the `Oneclient docker hub <https://hub.docker.com/r/onedata/oneclient/tags>`_.
 
 It's possible to use the most recent version by specifying the ``latest`` tag.
-We also recommend using same version as shown on the Onezone and
+We also recommend using the same version as shown on the Onezone and
 Oneprovider pages.
 
 The following variables have to be exported to be used in the container:
@@ -122,7 +122,7 @@ The following variables have to be exported to be used in the container:
    Getting configuration...
    Oneclient has been successfully mounted in '/mnt/oneclient'
 
-Now the client will run in the background and the data will now be available
+Now the client will run in the background and the data will be available
 through **samba/CIFS** or **nfs** protocols:
 
 .. code-block:: console
diff --git a/source/introduction.rst b/source/introduction.rst
index 3b0514d..9d8ba59 100644
--- a/source/introduction.rst
+++ b/source/introduction.rst
@@ -56,7 +56,7 @@ Highlighted features
    Viewing a data space in a console locally mounted using Oneclient
 
    Using Oneclient it's possible to mount a space locally, and access it over a
-   POSIX interface, using files as they were storred locally. The file's blocks
+   POSIX interface, using files as they were stored locally. The file's blocks
    are downloaded on demand.
 
 .. figure:: _static/datahub-replica-management.png
@@ -64,15 +64,15 @@ Highlighted features
 
    Viewing file distribution over the Oneproviders
 
-   In Onedata the file distribution is dong on a block basis, blocks will be
-   replicated on the fly, and it's possible to instrutmentize the replication.
+   In Onedata the file distribution is done on a block basis, blocks will be
+   replicated on the fly, and it's possible to instrument the replication.
 
 .. figure:: _static/datahub-metadata-management.png
    :alt: EGI DataHub metadata management
 
    Management of metadata using the web interface
 
-   Three different format of metadata can be attached to files: basic
+   Three different formats of metadata can be attached to files: basic
    (key/value), JSON and RDF. The metadata can be managed using the Web
    interface and the APIs. It's also possible to create indexes and query them.
 
diff --git a/source/providers.rst b/source/providers.rst
index 45219e1..92f070e 100644
--- a/source/providers.rst
+++ b/source/providers.rst
@@ -10,7 +10,7 @@ Transparent data access
 
 .. image:: _static/datahub-transparent-data-access.png
 
-* Clients uses one ore more providers to access data
+* Clients use one ore more providers to access data
 * Data can be accessed over multiple protocols
 
 Federation of service providers

GitHub sha: 5628209d