Adapted automation and console feature docs to reuse them as CrateDB-EE docs

docs/cluster/automation.md

@@ -1,17 +1,12 @@
 (cluster-automation)=
 # Automation
 
-Automation in CrateDB Cloud allows users to streamline and manage routine
+Automation allows users to streamline and manage routine
 database operations efficiently. Two primary automation features available are
 the SQL Scheduler and Table Policies, both of which facilitate the maintenance
 and optimization of database tasks.
 
-:::{important}
-- Automation is available for all newly deployed clusters.
-- For existing clusters, the feature can be enabled on demand. (Contact
-  [support](https://support.cratedb.com/) for activation.)
-
-Automation utilizes a dedicated database user `gc_admin` with full cluster
+Automation utilizes a dedicated database user with full cluster
 privileges to execute scheduled tasks and persists data in the `gc` schema.
 :::
 
@@ -20,9 +15,8 @@ privileges to execute scheduled tasks and persists data in the `gc` schema.
 The SQL Scheduler is designed to automate routine database tasks by scheduling
 SQL queries to run at specific times, in UTC time. This feature supports
 creating job descriptions with valid [cron patterns](https://www.ibm.com/docs/en/db2-as-a-service?topic=task-unix-cron-format)
-and SQL statements, enabling a wide range of tasks. Users can manage these jobs
-through the Cloud UI, adding, removing, editing, activating, and deactivating
-them as needed.
+and SQL statements, enabling a wide range of tasks. Users can manage these jobs 
+by adding, removing, editing, activating, and deactivating them as needed.
 
 ### Use Cases
 
@@ -137,7 +131,7 @@ A new policy can be created with the "Add New Policy" button.
 After naming the policy and selecting the table to be impacted, you
 must specify the time column. This column, which should be a timestamp used for
 partitioning, will determine the data affected by the policy. If you have multiple 
-partitioned tables you will need to setup a policy per table.
+partitioned tables you will need to set up a policy per table.
 
 :::{note}
 The "Time Column" must be of type `TIMESTAMP`.

docs/cluster/console.md

@@ -1,9 +1,8 @@
 (cluster-console)=
 # Console
 
-The Console in CrateDB Cloud allows users to execute SQL queries seamlessly
-against their CrateDB cluster. The Console can be accessed by users having the
-"Organization Admin" role in the left-hand navigation menu within a cluster.
+The Console allows users to execute SQL queries seamlessly
+against their CrateDB cluster.
 
 - **Table and Schema Tree View:** Easily navigate through your database 
   structure.
@@ -12,15 +11,6 @@ against their CrateDB cluster. The Console can be accessed by users having the
 - **Multiple Query Execution:** Run several queries in sequence.
 - **Query History:** Access and manage your past queries.
 
-:::{important}
-- The Console is available for all newly deployed clusters.
-- For older clusters, this feature can be enabled on demand. Contact 
-  [support](https://support.cratedb.com/) for activation.
-
-The Console currently utilizes a dedicated database user `gc_admin` with full 
-cluster privileges.
-:::
-
 :::{note}
 **Multi-Query Execution:**
 When running multiple queries at once, the Console executes them sequentially, 
@@ -30,7 +20,7 @@ between queries.
 :::
 
 :::{note}
-Each CrateDB Cloud cluster offers a dedicated {ref}`Admin UI <crate-admin-ui:index>`,
+Each cluster offers a dedicated {ref}`Admin UI <crate-admin-ui:index>`,
 which can be used to explore data, schema metadata, and cluster status
 information.
 :::