Rename page

Author: maxvp

public/_redirects

@@ -1643,6 +1643,7 @@
 /cloudflare-one/identity/users/short-lived-certificates/ /cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access/ 301
 /cloudflare-one/identity/users/validating-json/ /cloudflare-one/identity/authorization-cookie/validating-json/ 301
 /cloudflare-one/policies/lists/ /cloudflare-one/policies/gateway/lists 301
+/cloudflare-one/policies/gateway/dns-policies/scheduled-dns-policies/ /cloudflare-one/policies/gateway/timed-dns-policies/#scheduled-policies 301
 /cloudflare-one/policies/zero-trust/ /cloudflare-one/policies/access/ 301
 /cloudflare-one/policies/zero-trust/app-paths/ /cloudflare-one/policies/access/app-paths/ 301
 /cloudflare-one/policies/zero-trust/common-configs/ /cloudflare-one/policies/access/ 301

src/content/docs/cloudflare-one/policies/gateway/dns-policies/scheduled-dns-policies.mdx renamed to src/content/docs/cloudflare-one/policies/gateway/dns-policies/timed-dns-policies.mdx

@@ -1,22 +1,23 @@
 ---
 pcx_content_type: reference
-title: Scheduled DNS policies
+title: Timed DNS policies
 sidebar:
   order: 3
-
 ---
 
 Cloudflare Gateway allows you to configure any DNS policy to activate or deactivate on a regular time interval.
 
+## Scheduled policies
+
 By default, Gateway policies are unscheduled and apply at all times. You can use the [Gateway Rules API](/api/operations/zero-trust-gateway-rules-create-zero-trust-gateway-rule) to create a new DNS policy with a schedule or add a schedule to an existing policy. To schedule a policy, send a [`POST`](/api/operations/zero-trust-gateway-rules-create-zero-trust-gateway-rule) or [`PUT`](/api/operations/zero-trust-gateway-rules-update-zero-trust-gateway-rule) request with the `schedule` parameter set to your desired days of the week, times of day, and an optional time zone. The schedule will appear in Zero Trust under **Gateway** > **Firewall Policies** > **DNS** when you expand the row for the policy.
 
-## How Gateway determines time zone
+### How Gateway determines time zone
 
 If you [assign a time zone](#example-fixed-time-zone) to your schedule, Gateway will always use the current time at that time zone regardless of the user's location. This allows you to enable a policy during a certain fixed time period.
 
 If you [do not specify a time zone](#example-users-time-zone), Gateway will enable the DNS policy based on the user's local time zone. The user's time zone is inferred from the IP geolocation of their source IP address. If Gateway is unable to determine the time zone from the source IP, we will fall back to the time zone of the data center where the query was received.
 
-### Example: Fixed time zone
+#### Example: Fixed time zone
 
 The following command creates a DNS policy to block `facebook.com` only on weekdays from 8:00 AM - 12:30 PM and 1:30 PM - 5:00 PM in the Chicago, USA time zone.
 
@@ -43,7 +44,7 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules"
 
 Refer to [this table](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List) for a list of all time zones.
 
-### Example: User's time zone
+#### Example: User's time zone
 
 The following command creates a DNS policy to block `clockin.com` only on weekends, in the time zone where the user is currently located.
 
@@ -66,5 +67,5 @@ curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules"
 
 :::note
 
-Gateway will not change the policy's `enabled` status when inside or outside of the time period specified. When enabled, Gateway activates or deactivates the policy according to its schedule. When disabled, the policy is always deactivated. 
+Gateway will not change the policy's `enabled` status when inside or outside of the time period specified. When enabled, Gateway activates or deactivates the policy according to its schedule. When disabled, the policy is always deactivated.
 :::