rename oCIS web to oC Web

deployments/examples/ocis_keycloak/.env

@@ -15,7 +15,7 @@ TRAEFIK_ACME_MAIL=
 OCIS_DOCKER_TAG=
 # Domain of oCIS, where you can find the frontend. Defaults to "ocis.owncloud.test"
 OCIS_DOMAIN=
-# oCIS web openid connect client id. Defaults to "ocis-phoenix"
+# owncloud Web openid connect client id. Defaults to "ocis-phoenix"
 OCIS_OIDC_CLIENT_ID=
 
 ### Keycloak ###

deployments/examples/owncloud10_with_oc_web/README.md

@@ -2,5 +2,5 @@
 document this deployment example in docs/ocis/deployment/ocis_oc10_backend.md
 ---
 
-Please refer to [our documentation](https://owncloud.github.io/ocis/deployment/ocis_oc10_backend/)
+Please refer to [our documentation](https://owncloud.github.io/ocis/deployment/owncloud10_with_oc_web/)
 for instructions on how to deploy this scenario.

docs/extensions/ocis-phoenix/_index.md

@@ -1,5 +1,5 @@
 ---
-title: "oCIS Web"
+title: "ownCloud Web"
 date: 2018-05-02T00:00:00+00:00
 weight: 20
 geekdocRepo: https://github.com/owncloud/ocis
@@ -7,6 +7,6 @@ geekdocEditPath: edit/master/docs/extensions/ocis-phoenix
 geekdocFilePath: _index.md
 ---
 
-Note: Work in progress to rename Phoenix to oCIS Web.
+Note: Work in progress to rename Phoenix to ownCloud Web.
 
 This service embeds [Phoenix](https://github.com/owncloud/phoenix) to provide a UI for ownCloud Infinite Scale.

docs/ocis/deployment/_index.md

@@ -22,6 +22,6 @@ oCIS deployments are super simple, yet there are many configurations possible fo
 ### Migrate an existing ownCloud 10
 You can run ownCloud 10 and oCIS together. This allows you to use new parts of oCIS already with ownCloud 10 and also to have a smooth transition for users from ownCloud 10 to oCIS.
 
-- [ownCloud 10 setup with oCIS serving oCIS web and acting as OIDC provider]({{< ref "owncloud10_with_ocis_web.md" >}}) - This allows you to switch between the traditional ownCloud 10 frontend and the new oCIS web frontend
+- [ownCloud 10 setup with oCIS serving ownCloud Web and acting as OIDC provider]({{< ref "owncloud10_with_oc_web.md" >}}) - This allows you to switch between the traditional ownCloud 10 frontend and the new ownCloud Web frontend
 - Run ownCloud 10 and oCIS in parallel - together
 - Migrate users from ownCloud 10 to oCIS

docs/ocis/deployment/ocis_keycloak.md

@@ -66,7 +66,7 @@ See also [example server setup]({{< ref "preparing_server.md" >}})
   OCIS_DOCKER_TAG=
   # Domain of oCIS, where you can find the frontend. Defaults to "ocis.owncloud.test"
   OCIS_DOMAIN=
-  # oCIS web openid connect client id. Defaults to "ocis-phoenix"
+  # ownCloud Web openid connect client id. Defaults to "ocis-phoenix"
   OCIS_OIDC_CLIENT_ID=
 
   ### Keycloak ###
@@ -89,11 +89,11 @@ See also [example server setup]({{< ref "preparing_server.md" >}})
 
   Traefik will issue certificates with LetsEncrypt and therefore you must set an email address in `TRAEFIK_ACME_MAIL=`.
 
-  oCIS will by default started in the `latest` version. If you want to start a specific version of oCIS set the version to `OCIS_DOCKER_TAG=`. Available versions can be found on [Docker Hub](https://hub.docker.com/r/owncloud/ocis/tags?page=1&ordering=last_updated).
+  By default ocis will be started in the `latest` version. If you want to start a specific version of oCIS set the version to `OCIS_DOCKER_TAG=`. Available versions can be found on [Docker Hub](https://hub.docker.com/r/owncloud/ocis/tags?page=1&ordering=last_updated).
 
   Set your domain for the oCIS frontend in `OCIS_DOMAIN=`, eg. `OCIS_DOMAIN=ocis.owncloud.test`.
 
-  If you want to change the OIDC client id of th oCIS web frontend, you can do this by setting the name to `OCIS_OIDC_CLIENT_ID=`.
+  If you want to change the OIDC client id of th ownCloud Web frontend, you can do this by setting the name to `OCIS_OIDC_CLIENT_ID=`.
 
   Set your domain for the Keycloak adminstration panel and authentication endpoints to `KEYCLOAK_DOMAIN=` eg. `KEYCLOAK_DOMAIN=keycloak.owncloud.test`.
 
@@ -118,7 +118,7 @@ For a more simple local ocis setup see [Getting started]({{< ref "../getting-sta
 
 This docker stack can also be run locally. One downside is that Traefik can not obtain valid SSL certificates and therefore will create self signed ones. This means that your browser will show scary warnings. Another downside is that you can not point DNS entries to your localhost. So you have to add static host entries to your computer.
 
-On Linux you can add them to your `/etc/hosts` files like this:
+On Linux and macOS you can add them to your `/etc/hosts` files like this:
 ```
 127.0.0.1 ocis.owncloud.test
 127.0.0.1 traefik.owncloud.test

docs/ocis/deployment/owncloud10_with_oc_web.md

@@ -1,15 +1,15 @@
 ---
-title: "ownCloud 10 with oCIS Web"
+title: "ownCloud 10 with ownCloud Web"
 date: 2020-10-12T14:04:00+01:00
 weight: 25
 geekdocRepo: https://github.com/owncloud/ocis
 geekdocEditPath: edit/master/docs/ocis/deployment
-geekdocFilePath: owncloud10_with_ocis_web.md
+geekdocFilePath: owncloud10_with_oc_web.md
 ---
 
 {{< toc >}}
 
-This deployment scenario shows how to use oCIS Web as frontend for an existing ownCloud 10 production installation. It enables ownCloud 10 users to log in and work with their files using the new ownCloud Web. While the scenario includes an ownCloud 10 instance, it only exists to show the necessary configuration for your already existing ownCloud 10 installation.
+This deployment scenario shows how to use ownCloud Web as frontend for an existing ownCloud 10 production installation. It enables ownCloud 10 users to log in and work with their files using the new ownCloud Web. While the scenario includes an ownCloud 10 instance, it only exists to show the necessary configuration for your already existing ownCloud 10 installation.
 
 ## Overview
 
@@ -19,7 +19,7 @@ This deployment scenario shows how to use oCIS Web as frontend for an existing o
 * DNS is resolving one domain for ocis and one for oc10
 * Valid ssl certificates for the domains for ssl termination
 
-[Find this example on GitHub](https://github.com/owncloud/ocis/tree/master/deployments/examples/ocis_external_konnectd)
+[Find this example on GitHub](https://github.com/owncloud/ocis/tree/master/deployments/examples/owncloud10_with_oc_web)
 
 {{< hint info >}}
 In this setup it's mandatory that the users in ownCloud 10 are assigned to at least one group.
@@ -116,4 +116,4 @@ After that you're ready to start the application stack:
 
 `docker-compose up -d`
 
-Open https://oc10.owncloud.test in your browser and accept the invalid certificate warning. You now can login with the ownCloud 10 default user "admin" and password "admin". As you might have noticed, you did not see the login prompt of ownCloud 10. This was the login prompt of oCIS. When you go to application you can both in oCIS web and ownCloud 10 see a switch to switch vice versa.
+Open https://oc10.owncloud.test in your browser and accept the invalid certificate warning. You now can login with the ownCloud 10 default user "admin" and password "admin". As you might have noticed, you did not see the login prompt of ownCloud 10. This was the login prompt of oCIS. When you go to application you can both in ownCloud Web and ownCloud 10 see a switch to switch vice versa.

docs/ocis/getting-started.md

@@ -45,7 +45,7 @@ docker run --rm -ti -p 9200:9200 owncloud/ocis
 
 ## Usage
 
-### Login to oCIS Web
+### Login to ownCloud Web
 
 Open [https://localhost:9200](https://localhost:9200) and login using one of the demo accounts: