fix(rdb): cron pt 4

Author: ldecarvalho-doc

pages/managed-databases-for-postgresql-and-mysql/api-cli/using-pgcron.mdx

@@ -144,35 +144,31 @@ SELECT cron.unschedule('nightly-vacuum');
 
 ## Scheduling jobs in other databases
 
-To schedule a job in another database, you can use the `schedule_in_database` function:
+To schedule a job in another database, you can use the `schedule_in_database` function.
 
-```sql
-SELECT cron.unschedule('${JOB_ID}');
-```
+In the example below we create a job to insert values into another table.
 
 ```sql
 SELECT cron.schedule_in_database('job-in-another-db', '0 12 * * *', 'INSERT INTO public.another_db_table values (now())', 'mydb');
-schedule
-----------
-3
 ```
+<Message type="note">
+  The `cron.schedule_in_database` function runs jobs as the user who created them. Therefore, you need to connect as said user to execute the job. This function does not allow specifying a different user, as it would require superuser privileges.
+</Message>
 
-Note that cron.schedule_in_database runs jobs as the user who created them, so you'll need to connect as that user to execute the job.
-Additionally, this function doesn't allow specifying a different user, as it would require superuser privileges.
 
-**Editing Jobs**
+## Editing Jobs
 
-To edit a job, you can use the `alter_job` function:
+To edit a job, you can use the `alter_job` function.
+
+In the example below
 
 ```sql
 SELECT cron.alter_job(job_id:=3,database:='anotherdb');
--[ RECORD 1 ]
-alter_job |
 ```
 
-**Cron Syntax**
+## Cron specifications
 
-The schedule uses the standard cron syntax:
+Schedules in `pgcron` use the standard Cron syntax:
 
 ```
 ┌───────────── min (0 - 59)
@@ -186,6 +182,20 @@ The schedule uses the standard cron syntax:
 * * * * *
 ```
 
-**Time Zone**
+<Message type="tip">
+  Refer to the [Cron schedules reference](/serverless-jobs/reference-content/cron-schedules/) for a detailed explanation of the cron format and examples.
+</Message>
+
+### How to configure your schedule timezone
+
+The time zone of the `pg_cron` extension can be changed in the advanced settings of the Database Instance. By default, the time zone is set to GMT.
 
-The time zone of the pg_cron extension can be changed in the advanced settings of the instance: `cron.timezone`. By default, the time zone is set to GMT.
+1. Go to the **Advanced settings** of your Database Instance in the Scaleway console.
+   2. Click <Icon name="edit" />.
+   3. Click **+ Add parameters**.
+   4. Select `cron.timezone` in the drop-down.
+   5. Enter the time zone of your choice.
+   6. Click <Icon name="validate" /> to validate.
+      <Message type="note">
+        The configuration takes a few seconds to be applied. During this time the Database Instance connection remains uninterrupted. However, you must wait until the new configuration is applied to edit your advanced settings again.
+      </Message>