From 4935c50ecc1eb5e793a346d2057ca337409558bd Mon Sep 17 00:00:00 2001 From: Amit Lichtenberg Date: Tue, 21 May 2024 08:27:35 +0300 Subject: [PATCH] touchups --- docs/features/mysql/tutorials/mysql.mdx | 4 ++-- docs/features/postgresql/tutorials/postgres.mdx | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/features/mysql/tutorials/mysql.mdx b/docs/features/mysql/tutorials/mysql.mdx index 2748ecd9e..6217dfb90 100644 --- a/docs/features/mysql/tutorials/mysql.mdx +++ b/docs/features/mysql/tutorials/mysql.mdx @@ -156,7 +156,7 @@ This applies the following `MySQLServerConfig` to your cluster, and patches it w ``` The above CRD tells Otterize how to access a database instance named `mysql-tutorial-db`, meaning that when intents -are applied requesting access permissions to `mysql-tutorial-db`, Otterize operators will be able to configure +are applied requesting access permissions to `mysql-tutorial-db`, the Otterize operator will be able to configure them. In this tutorial, we use the admin user to grant Otterize permissions to create users and grant them access to the database. @@ -177,7 +177,7 @@ Specifying the table and operations is optional. If you don't specify the table, ```yaml {@include: ../../../../static/code-examples/mysql/clientintents.yaml} ``` -We can now apply our intents. Behind the scenes,the Otterize credentials-operator created the user for our `server` workload while the intents-operator ran `GRANT` queries on the database, making our `SELECT` and `INSERT` errors disappear. +We can now apply our intents. Behind the scenes, the Otterize operator created the user for our `server` workload and executed `GRANT` queries on the database, making our `SELECT` and `INSERT` errors disappear. ```shell kubectl apply -n otterize-tutorial-mysql -f ${ABSOLUTE_URL}/code-examples/mysql/clientintents.yaml diff --git a/docs/features/postgresql/tutorials/postgres.mdx b/docs/features/postgresql/tutorials/postgres.mdx index ddf7e2bee..d1a37309e 100644 --- a/docs/features/postgresql/tutorials/postgres.mdx +++ b/docs/features/postgresql/tutorials/postgres.mdx @@ -63,7 +63,7 @@ To deploy Otterize, head over to [Otterize Cloud](https://app.otterize.com) and ### Deploy tutorial services and request database credentials This will set up the namespace we will use for our tutorial and deploy the client, server, and database. -Our server's Deployment spec will specify an annotation on the Pod, which requests that the credentials operator will provision a username and password for the server. +Our server's Deployment spec will specify an annotation on the Pod, which requests that the Otterize operator will provision a username and password for the server. ```yaml template: metadata: @@ -83,7 +83,7 @@ kubectl apply -n otterize-tutorial-postgres -f ${ABSOLUTE_URL}/code-examples/pos {@include: ../../../../static/code-examples/postgres/postgresqlserverconfig.yaml} ``` The above CRD tells Otterize how to access a database instance named `postgres-tutorial-db`, meaning that when intents -are applied requesting access permissions to `postgres-tutorial-db`, Otterize operators will be able to configure +are applied requesting access permissions to `postgres-tutorial-db`, the Otterize operator will be able to configure them. In this tutorial, the `database` workload already comes with the predefined username & password, but for future uses a @@ -122,7 +122,7 @@ Specifying the table and operations is optional. If you don't specify the table, {@include: ../../../../static/code-examples/postgres/clientintents.yaml} ``` -We can now apply our intents. Behind the scenes,the Otterize credentials-operator created the user for our `server` workload while the intents-operator ran `GRANT` queries on the database, making our `SELECT` and `INSERT` errors disappear. +We can now apply our intents. Behind the scenes, the Otterize operator created the user for our `server` workload and executed `GRANT` queries on the database, making our `SELECT` and `INSERT` errors disappear. ```shell kubectl apply -n otterize-tutorial-postgres -f ${ABSOLUTE_URL}/code-examples/postgres/clientintents.yaml