diff --git a/v23.1/alter-backup-schedule.md b/v23.1/alter-backup-schedule.md
index 9fb7e314265..00d3945a97b 100644
--- a/v23.1/alter-backup-schedule.md
+++ b/v23.1/alter-backup-schedule.md
@@ -48,12 +48,6 @@ You can use the backup options in this table to control the behavior of your bac
 
 ### Schedule options
 
-{{site.data.alerts.callout_danger}}
-**The following schedule options are in preview.**  Their interface, options, and outputs are subject to change, and there may be bugs.
-
-If you encounter a bug, please [file an issue](file-an-issue.html).
-{{site.data.alerts.end}}
-
 You can use the schedule options in this table to control the behavior of your backup schedule. See [Apply different options to scheduled backups](#apply-different-options-to-scheduled-backups) for an example.
 
 {% include {{ page.version.version }}/backups/schedule-options.md %}
diff --git a/v23.1/create-schedule-for-backup.md b/v23.1/create-schedule-for-backup.md
index a5efdece8ea..97d0e568193 100644
--- a/v23.1/create-schedule-for-backup.md
+++ b/v23.1/create-schedule-for-backup.md
@@ -60,7 +60,7 @@ Targets:
 `backup_options`                        | Control the backup behavior with a comma-separated list of [options](#backup-options).
 `RECURRING crontab`                     | Specifies when the backup should be taken. A separate schedule may be created automatically to write full backups at a regular cadence, depending on the frequency of the incremental backups. You can likewise modify this separate schedule with [`ALTER BACKUP SCHEDULE`](alter-backup-schedule.html). The schedule is specified as a [`STRING`](string.html) in [crontab format](https://en.wikipedia.org/wiki/Cron). All times in UTC. <br><br>Example: `'@daily'` (run daily at midnight)
 <a name="full-backup-clause"></a>`FULL BACKUP crontab` | Specifies when to take a new full backup. The schedule is specified as a [`STRING`](string.html) in [crontab format](https://en.wikipedia.org/wiki/Cron) or as `ALWAYS`. <br><br>If `FULL BACKUP ALWAYS` is specified, then the backups triggered by the `RECURRING` clause will always be full backups. <br>**Note:** If you do not have an Enterprise license then you can only take full backups. `ALWAYS` is the only accepted value of `FULL BACKUP`.<br><br>If the `FULL BACKUP` clause is omitted, CockroachDB will default to the following full backup schedule: <ul><li>`RECURRING` <= 1 hour: Default to `FULL BACKUP '@daily'`</li><li>`RECURRING` <= 1 day: Default to `FULL BACKUP '@weekly'`</li><li>Otherwise: Default to `FULL BACKUP ALWAYS`</li></ul>
-`WITH SCHEDULE OPTIONS schedule_option` | _Experimental feature._ Control the schedule behavior with a comma-separated list of [these options](#schedule-options).
+`WITH SCHEDULE OPTIONS schedule_option` | Control the schedule behavior with a comma-separated list of [these options](#schedule-options).
 
 {{site.data.alerts.callout_info}}
 For schedules that include both [full and incremental backups](take-full-and-incremental-backups.html), CockroachDB will create two schedules (one for each type).
@@ -72,10 +72,6 @@ For schedules that include both [full and incremental backups](take-full-and-inc
 
 ### Schedule options
 
-{{site.data.alerts.callout_info}}
-{% include feature-phases/preview.md %}
-{{site.data.alerts.end}}
-
 {% include {{ page.version.version }}/backups/schedule-options.md %}
 
 ## Considerations