global: typo and phrasing fixes

Co-Authored-By: fenekku <[email protected]>

Author: 2 people

docs/develop/customize.md

@@ -22,6 +22,6 @@ Passing the `--no-install-js` option, skips re-installation of JS dependencies.
 Go to the browser [*https://localhost:5000/*](https://localhost:5000) or refresh the page. And voilà! The logo has been changed!
 
 !!! warning "That evil cache"
-    If you do not see it changing, check in an incognito window, the browser might have cached the logo.
+    If you do not see it changing, check in an incognito window; the browser might have cached the logo.
 
 Need further customizations? Have you thought of creating your own extensions? How to add them to your InvenioRDM instance is explained in the next section - [here](../extensions/custom.md).

docs/extensions/custom.md

@@ -1,9 +1,9 @@
 # Extensions
 
-If you need to add custom functionalaty to your RDM instance you need to develop your own module. You can start it by using the [cookiecutter-invenio-module](https://github.com/inveniosoftware/cookiecutter-invenio-module) template. It will get you started in no time.
+If you want to add custom functionality to your RDM instance, you need to develop your own module. You can start in no time by using the [cookiecutter-invenio-module](https://github.com/inveniosoftware/cookiecutter-invenio-module) template.
 
 ## Create your module
-Lets assume you have already done so:
+Let's run the cookiecutter:
 
 ``` console
 $ cookiecutter https://github.com/inveniosoftware/cookiecutter-invenio-module
@@ -13,10 +13,11 @@ $ cookiecutter https://github.com/inveniosoftware/cookiecutter-invenio-module
 
 ## Add your functionality
 
-And you have added a simple view to the blue print in the `<your_custom_module>/views.py`, which looks like:
+We've added a simple view to the blueprint in `<your_custom_module>/views.py`, which looks like:
 
 ``` python
-[...]
+# Other code ignored for clarity
+
 blueprint = Blueprint(
     'invenio_rdm_extension_demo',
     __name__
@@ -38,7 +39,7 @@ $ cd path/to/your/instance
 $ pipenv install [--pre] -e path/to/your/extension
 ```
 
-As you can see, `--pre` is optional, it is only needed when the package is in a pre-release state. In addition, note that you do not need to specify a local path, if the package is available e.g. via PyPi you can just install it by its name.
+As you can see, `--pre` is optional. It is only needed when the package is in a pre-release state. In addition, note that you do not need to specify a local path. If the package is available e.g. via PyPi, you can just install it by its name.
 
 ## Sanity check and run!
 

docs/extensions/index.md

@@ -6,4 +6,4 @@ InvenioRDM supports a great variety of extensions that can help you adapt it to
 
 ### Storage
 
-- [S3](s3.md)
+- [S3](s3.md) can be configured to serve as your storage backend via the [invenio-s3](https://github.com/inveniosoftware/invenio-s3) extension. If you chose S3 as storage when initializing your instance, [navigate here](#i-chose-s3-when-initializing-the-repository). Otherwise, [navigate to this section](#i-didnt-choose-s3-when-initializing).

docs/extensions/s3.md

@@ -2,13 +2,13 @@
 
 ## I chose S3 when initializing the repository!
 
-If you are reading the section you are lucky! you will only have to perform a few configuration changes. If on the contrary you didn't choose S3 as storage when initializing the repository file system, [navigate below](#i-didnt-choose-s3-when-initializing) to follow more in depth changes!
+If you are reading this section, you are lucky! You will only have to perform a few configuration changes. If on the contrary you didn't choose S3 as storage when initializing the repository file system, [navigate below](#i-didnt-choose-s3-when-initializing) to follow more in depth instructions!
 
 ### Create a bucket
 
-InvenioRDM uses a [minio](https://min.io/download) container for S3 alike storage. To create a bucket in minio you can:
+InvenioRDM uses a [MinIO](https://min.io/download) container for S3-like storage. To create a bucket in MinIO you can:
 
-a. Install the [mc tool](https://docs.min.io/docs/minio-client-quickstart-guide.html) and run the following command, where `defaul-bucket` is the name of your bucket.
+a. Install the [mc tool](https://docs.min.io/docs/minio-client-quickstart-guide.html) and run the following command, where `default-bucket` is the name of your bucket.
 
 ``` console
 $ mc mb default-bucket
@@ -18,7 +18,7 @@ b. Use the web UI (https://localhost[:9000]/minio). In the bottom right you will
 
 ### Create a new location
 
-Now you need to tell InvenioRDM where is that bucket, for that create a new location. If you are running a local (development) instance, run:
+Now you need to tell InvenioRDM where that bucket is. For that, create a new location. If you are running a local (development) instance, run:
 
 ``` console
 $ cd path/to/your/instance
@@ -28,20 +28,20 @@ $ pipenv run invenio files location s3-default s3://default-bucket --default
 If you are running the containerized version, run:
 
 ``` console
-$ docker exec -it < web_[api|ui] container name or id> /bin/bash
-$ invenio files location s3-default s3://default-bucket --default
+$ docker exec -it <web_[api|ui] container name or id> /bin/bash
+$ invenio files location create s3-default s3://default-bucket --default
 ```
 
 ### Set your credentials
 
 The last step is to set your credentials so your instance can authenticate against the S3 container.
 
-By default the `ACCESS_KEY` and the `ACCESS_ID` of minio are "CHANGE_ME", and so they are set in the `invenio.cfg` file. If you changed them (you should) modify them accordingly in the config file.
+By default, the `ACCESS_KEY` and the `ACCESS_ID` of MinIO are "CHANGE_ME", and so they are set in the `invenio.cfg` file. If you changed them (you should) modify them accordingly in the config file.
 
 It's done! Ready to roll!
 
 ## I didn't choose S3 when initializing
 
 You are here, but do not panic, is not difficult just longer.
 
-This docs will come soon, for now we apologize for the hussle, but could you create a new instance to test S3?
+Coming soon.

docs/index.md

@@ -39,7 +39,7 @@ the workflow to be effective with them.
 
 ## Extensions
 
-InvenioRDM supports a great variety of extensions that can help you adapt it to your infrastructure, it also supports the addition of custom made ones.
+InvenioRDM supports a great variety of extensions that can adapt it to your infrastructure. It also supports the addition of custom made ones.
 
 [> Extensions setup](extensions/index.md)
 

docs/install/index.md

@@ -13,7 +13,7 @@ Some system requirements are needed beforehand:
 - [Docker-Compose](https://docs.docker.com/compose/) (1.17.0+)
 
 !!! warning "Other Python distributions"
-    InvenioRDM works with Python 3.6.2. However, many users have reported errors when running Python from Anaconda.
+    InvenioRDM targets CPython 3.6 (lowest 3.6.2). Anaconda Python in particular is not currently supported and other Python distributions are not tested.
 
 In addition, make sure the user that will be executing the CLI has access to
 the docker command (i.e. it is not only available for the root user):
@@ -23,7 +23,7 @@ $ sudo usermod --append --groups docker $USER
 ```
 
 !!! note "Hardware requirements"
-    We usually deploy the RDM in machines that have around 8GB of RAM and at least 4 cores. InvenioRDM can certainly run (for demo purposes) with less, just take into account that you are going to be runing between 4 and 8 containers (among them ES, which is quite demanging).
+    We usually deploy the RDM in machines that have around 8GB of RAM and at least 4 cores. InvenioRDM can certainly run (for demo purposes) with less, just take into account that you are going to be running between 4 and 8 containers (among them an Elasticsearch container, which is quite demanding).
 
 Once you have installed these requirements, you can install the CLI.
 
@@ -59,4 +59,4 @@ invenio-cli, version 0.10.0
 ```
 
 !!! note "CLI version"
-    The CLI is in pre 1.0 release. The last release's version is **0.10.0**. Your version may be different than the above.*
+    The CLI is in pre 1.0 release. The last release's version is **0.10.0**. Your version may be different than the above.