frouioui · bot-vitess · Jul 19, 2024 · Jul 19, 2024
diff --git a/content/en/blog/2024-07-22-an-interesting-optimisation.md b/content/en/blog/2024-07-22-an-interesting-optimisation.md
diff --git a/content/en/community.md b/content/en/community.md
@@ -26,11 +26,20 @@ We welcome your contribution to Vitess, whether they be documentation, a bug fix
 
 On the third Thursday of the month (unless otherwise specified), the Vitess community holds a monthly meeting by video conference to discuss the state of Vitess. New features will be previewed or discussed, and everyone regardless of location and familiarity with Vitess is welcome to join.
 
-To stay up to date on these meetings and join them, please subscribe to the [CNCF Public Events calendar](https://www.cncf.io/community/calendar/).
+To stay up to date on these meetings, subscribe to the [CNCF Public Events calendar](https://www.cncf.io/community/calendar/).
 
 **Date**: 3rd Thursday of every month
+
 **Time**: 08.00 a.m. PST
 
+**Dial-in details**: [Click to join Zoom call](https://zoom.us/j/8695363767?pwd=dmJ4V0h3aEhyei90VnMzYXlxRUZGdz09)
+
+To join by phone:
+
+* US: +16699006833,,8695363767#  or +16465588656,,8695363767#
+* International dial-in numbers [click here](../dialin)
+* Meeting ID (required to join the call): 8695363767
+
 If you would like to submit a topic for discussion at the meeting, please [email the maintainers team](mailto:[email protected]), or reply to the call-for-agenda-items on the Vitess Slack a few days before the call.
 
 [Notes and agenda items from past meetings](https://docs.google.com/document/d/1XLUdKePtj9aZD0E2Nlr3VRk1NIaSBgeIvXUj13y5CFk/edit)

diff --git a/content/en/dialin.md b/content/en/dialin.md
@@ -0,0 +1,31 @@
+---
+title: Vitess Monthly Meeting Dial-In Information 
+description: Details for dialing in to the monthly meeting 
+---
+
+We use Zoom for our monthly meeting. You can dial-in by phone from these countries with the following details.
+
+Using the Zoom app on mobile or web: [click here](https://zoom.us/j/8695363767?pwd=dmJ4V0h3aEhyei90VnMzYXlxRUZGdz09)
+
+Meeting ID: 8695363767
+
+**Joining by phone:**
+
+Or iPhone one-tap :
+
+ US: +16699006833,,8695363767# or +16465588656,,8695363767#
+
+**Or other phone:**
+
+Dial(for higher quality, dial a number based on your current location)：
+
+* US: +1 669 900 6833 or +1 646 558 8656 or +1 877 853 5247  (Toll Free) or +1 877 369 0926 (Toll Free)
+
+* China: 400 616 8835 or 400 669 9381 (China Toll-Free)
+* Canada: +1 855 703 8985 (Canada Toll-Free)
+* UK: +44 80 8189 4088 (United Kingdom Toll-Free)
+* Australia: +61 18 0079 2488 (Australia Toll-Free)
+* Japan: +81 (0) 800 100 5040 (Japan Toll-Free)
+
+If you do not see your country listed here, refer to [Zoom's international dial-in page](https://zoom.us/zoomconference).
+
diff --git a/content/en/docs/18.0/get-started/operator.md b/content/en/docs/18.0/get-started/operator.md
@@ -161,18 +161,6 @@ The schema has been simplified to include only those fields that are significant
 * The `customer` table has a `customer_id` that has an `auto_increment`. A typical customer table would have a lot more columns, and sometimes additional detail tables.
 * The `corder` table (named so because `order` is an SQL reserved word) has an `order_id` auto-increment column. It also has foreign keys into `customer(customer_id)` and `product(sku)`.
 
-## Common Issues and Solutions
-
-<b>Issue:</b> Starting Minikube produces the following error:
-```sh
-The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force. 
-If you are running minikube within a VM, consider using --driver=none: 
-https://minikube.sigs.k8s.io/docs/reference/drivers/none
-Exiting due to to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.
-``` 
-
-<b>Solution:</b> Create a new user and add it to your [docker group](https://docs.docker.com/engine/install/linux-postinstall).
-
 ## Next Steps
 
 You can now proceed with [MoveTables](../../user-guides/migration/move-tables).

diff --git a/content/en/docs/19.0/get-started/operator.md b/content/en/docs/19.0/get-started/operator.md
@@ -161,18 +161,6 @@ The schema has been simplified to include only those fields that are significant
 * The `customer` table has a `customer_id` that has an `auto_increment`. A typical customer table would have a lot more columns, and sometimes additional detail tables.
 * The `corder` table (named so because `order` is an SQL reserved word) has an `order_id` auto-increment column. It also has foreign keys into `customer(customer_id)` and `product(sku)`.
 
-## Common Issues and Solutions
-
-<b>Issue:</b> Starting Minikube produces the following error:
-```sh
-The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force. 
-If you are running minikube within a VM, consider using --driver=none: 
-https://minikube.sigs.k8s.io/docs/reference/drivers/none
-Exiting due to to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.
-``` 
-
-<b>Solution:</b> Create a new user and add it to your [docker group](https://docs.docker.com/engine/install/linux-postinstall).
-
 ## Next Steps
 
 You can now proceed with [MoveTables](../../user-guides/migration/move-tables).

diff --git a/content/en/docs/20.0/get-started/operator.md b/content/en/docs/20.0/get-started/operator.md
@@ -162,18 +162,6 @@ The schema has been simplified to include only those fields that are significant
 * The `customer` table has a `customer_id` that has an `auto_increment`. A typical customer table would have a lot more columns, and sometimes additional detail tables.
 * The `corder` table (named so because `order` is an SQL reserved word) has an `order_id` auto-increment column. It also has foreign keys into `customer(customer_id)` and `product(sku)`.
 
-## Common Issues and Solutions
-
-<b>Issue:</b> Starting Minikube produces the following error:
-```sh
-The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force. 
-If you are running minikube within a VM, consider using --driver=none: 
-https://minikube.sigs.k8s.io/docs/reference/drivers/none
-Exiting due to to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.
-``` 
-
-<b>Solution:</b> Create a new user and add it to your [docker group](https://docs.docker.com/engine/install/linux-postinstall).
-
 ## Next Steps
 
 You can now proceed with [MoveTables](../../user-guides/migration/move-tables).

diff --git a/content/en/docs/21.0/get-started/operator.md b/content/en/docs/21.0/get-started/operator.md
@@ -161,19 +161,6 @@ The schema has been simplified to include only those fields that are significant
 * The `customer` table has a `customer_id` that has an `auto_increment`. A typical customer table would have a lot more columns, and sometimes additional detail tables.
 * The `corder` table (named so because `order` is an SQL reserved word) has an `order_id` auto-increment column. It also has foreign keys into `customer(customer_id)` and `product(sku)`.
 
-## Common Issues and Solutions
-
-<b>Issue:</b> Starting Minikube produces the following error:
-```sh
-The "docker" driver should not be used with root privileges. If you wish to continue as root, use --force. 
-If you are running minikube within a VM, consider using --driver=none: 
-https://minikube.sigs.k8s.io/docs/reference/drivers/none
-Exiting due to to DRV_AS_ROOT: The "docker" driver should not be used with root privileges.
-``` 
-
-<b>Solution:</b> Create a new user and add it to your [docker group](https://docs.docker.com/engine/install/linux-postinstall).
-
-
 ## Next Steps
 
 You can now proceed with [MoveTables](../../user-guides/migration/move-tables).