Apply suggestions from code review

Co-authored-by: Lukas Hirt <info@hirt.cz>

Author: mmattel

docs/ocis/build-docs.md

@@ -47,14 +47,14 @@ When a docs PR gets merged, the content of the `docs/` folder gets "copied". For
 
 {{< hint info >}}
 * For building the documentation locally, you need to have `make`, `docker` and `go` installed.\
-  See the [ocis README](https://github.com/owncloud/ocis/#use-the-ocis-repo-as-source) for more details and minimum versions required.
+  See the [oCIS README](https://github.com/owncloud/ocis/#use-the-ocis-repo-as-source) for more details and minimum versions required.
 * Regulary, at least once after cloning, branching or rebasing, run `make generate` to update the assets. This ensures that all data that is accessed by the docs build process is up-to-date.
-* Run the make commands from the ocis root, the makefile contains all required targets.\
+* Run the make commands from the oCIS root, the makefile contains all required targets.\
 Use `make help` for more details.
 {{< /hint >}}
 
 * **For any changes**, you must fully build the documentation first to preview it.\
-For ease of working, open two terminals and change to the ocis root. The terminals are numberd as (1) and (2).
+For ease of working, open two terminals and change to the oCIS root. The terminals are numberd as (1) and (2).
   * At first start, from any terminal, run `sudo make docs-clean` to have a clean build environment.\
   sudo is required for deletion, because files generated by hugo, which runs in a container, are created by root.
   * Do all the doc changes required in the docs repository.