adjective order

Adjective order nit-correction in prepositions.

Dockerfile

@@ -11,7 +11,7 @@
 # `make -C ocis dev-docker`
 # It will build a `owncloud/ocis:dev` image for you
 # and use your local Yarn and Go caches and therefore
-# is a lot faster than the below build steps.
+# is a lot faster than the build steps below.
 
 
 FROM owncloudci/nodejs:14 as generate

docs/ocis/_index.md

@@ -15,7 +15,7 @@ Welcome to oCIS, the modern file-sync and share platform, which is based on our
 ### The idea of federated storage
 To create a truly federated storage architecture oCIS breaks down the old ownCloud 10 user specific namespace, which is assembled on the server side, and makes the individual parts accessible to clients as storage spaces and storage space registries.
 
-The below diagram shows the core concepts that are the foundation for the new architecture:
+The diagram below shows the core concepts that are the foundation for the new architecture:
 - End user devices can fetch the list of *storage spaces* a user has access to, by querying one or multiple *storage space registries*. The list contains a unique endpoint for every *storage space*.
 - [*Storage space registries*]({{< ref "./storage/terminology#storage-space-registries" >}}) manage the list of storage spaces a user has access to. They may subscribe to *storage spaces* in order to receive notifications about changes on behalf of an end users mobile or desktop client.
 - [*Storage spaces*]({{< ref "./storage/terminology#storage-spaces" >}}) represent a collection of files and folders. A users personal files are contained in a *storage space*, a group or project drive is a *storage space*, and even incoming shares are treated and implemented as *storage spaces*. Each with properties like owners, permissions, quota and type.
@@ -61,6 +61,6 @@ We run a huge [test suite](https://github.com/owncloud/core/tree/master/tests),
 
 ### Architecture Overview
 
-Running `bin/ocis server` will start the below services, all of which can be scaled and deployed on a single node or in a cloud native environment, as needed.
+Running `bin/ocis server` will start the following services, all of which can be scaled and deployed on a single node or in a cloud native environment, as needed.
 
 {{< figure src="/ocis/static/architecture-overview.drawio.svg" >}}

docs/ocis/deployment/bridge.md

@@ -71,7 +71,7 @@ $ make -C ocis build
 This should give you an `ocis/bin/ocis` binary. Try listing the help with `ocis/bin/ocis --help`.
 
 {{< hint >}}
-You can check out a custom branch and build a custom binary which can then be used for the below steps.
+You can check out a custom branch and build a custom binary which can then be used for the steps below.
 {{< /hint >}}
 
 ### Start ocis glauth

docs/ocis/storage/users.md

@@ -46,7 +46,7 @@ For the format of the users.json have a look at the [reva examples](https://gith
 
 This is the default user driver.
 
-If the below defaults don't match your environment change them accordingly:
+If the following defaults don't match your environment then change them accordingly:
 ```
 export STORAGE_LDAP_HOSTNAME=localhost
 export STORAGE_LDAP_PORT=9126

docs/services/settings/tests.md

@@ -61,9 +61,9 @@ ocis init
 OCIS_URL=https://host.docker.internal:9200 OCIS_INSECURE=true PROXY_ENABLE_BASIC_AUTH=true WEB_UI_CONFIG=../../web/dev/docker/ocis.web.config.json ./bin/ocis server
 ```
 
-If you've built the web bundle locally in its repository, you also need to reference the bundle output in the above command: `WEB_ASSET_PATH=../../web/dist`
+If you've built the web bundle locally in its repository, you also need to reference the bundle output in the command above: `WEB_ASSET_PATH=../../web/dist`
 
-If you've built the settings UI bundle locally, you also need to reference the bundle output in the above command: `SETTINGS_ASSET_PATH=../settings/assets/`
+If you've built the settings UI bundle locally, you also need to reference the bundle output in the command above: `SETTINGS_ASSET_PATH=../settings/assets/`
 
 #### Run settings acceptance tests
 

ocis-pkg/config/envdecode/README.md

@@ -57,7 +57,7 @@ All parse errors will fail fast and return an error in this mode.
 ## Supported types
 
 - Structs (and pointer to structs)
-- Slices of below defined types, separated by semicolon
+- Slices of defined types below, separated by semicolon
 - `bool`
 - `float32`, `float64`
 - `int`, `int8`, `int16`, `int32`, `int64`