[Workers] format revision (cloudflare#3216)

* [Workers] format fix

* [Workers] format revision

* remove backticks

* spacing

Author: deadlypants1973

products/workers/src/content/platform/compatibility-dates.md

@@ -1,5 +1,4 @@
 ---
-order: 10
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/cron-triggers/index.md

@@ -1,5 +1,4 @@
 ---
-order: 9
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/deploy-button.md

@@ -1,5 +1,4 @@
 ---
-order: 8
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/environment-variables.md

@@ -1,5 +1,4 @@
 ---
-order: 7
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/environments.md

@@ -1,5 +1,4 @@
 ---
-order: 6
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/known-issues.md

@@ -1,5 +1,4 @@
 ---
-order: 5
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/languages.md

@@ -1,5 +1,4 @@
 ---
-order: 1
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/limits.md

@@ -1,5 +1,4 @@
 ---
-order: 2
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/pricing.md

@@ -1,5 +1,4 @@
 ---
-order: 3
 pcx-content-type: concept
 ---
 

products/workers/src/content/platform/routes.md

@@ -1,5 +1,4 @@
 ---
-order: 4
 pcx-content-type: concept
 ---
 

products/workers/src/content/runtime-apis/headers.md

@@ -37,24 +37,45 @@ Cloudflare sets a number of [its own custom headers on incoming requests](https:
 
 ### Request headers
 
-* `CF-Connecting-IP`: In same-zone Worker subrequests, the value of `CF-Connecting-IP` reflects the value of `x-real-ip` (the client’s IP). `x-real-ip` can be altered by the user in their Worker script.
+<details>
+<summary>CF-Connecting-IP</summary>
+<div>
 
-    In cross-zone subrequests from one Cloudflare customer zone to another Cloudflare customer zone, the `CF-Connecting-IP` value will be set to the Worker client IP address `'2a06:98c0:3600::103'` for security reasons. 
+In same-zone Worker subrequests, the value of `CF-Connecting-IP` reflects the value of `x-real-ip` (the client’s IP). `x-real-ip` can be altered by the user in their Worker script.
 
-    For Worker subrequests destined for a non-Cloudflare customer zone, the `CF-Connecting-IP` and `x-real-ip` headers will both reflect the client's IP address, with only the `x-real-ip` header able to be altered.
+In cross-zone subrequests from one Cloudflare customer zone to another Cloudflare customer zone, the `CF-Connecting-IP` value will be set to the Worker client IP address `'2a06:98c0:3600::103'` for security reasons. 
 
-    When no Worker subrequest is triggered, `cf-connecting-ip` reflects the client's IP address and the `x-real-ip` header is stripped.
+For Worker subrequests destined for a non-Cloudflare customer zone, the `CF-Connecting-IP` and `x-real-ip` headers will both reflect the client's IP address, with only the `x-real-ip` header able to be altered.
 
-* `CF-Worker`: Added to all Worker subrequests sent via `fetch()`. Set to the name of the zone which owns the Worker making the subrequest. For example, a Worker script on route for `foo.example.com/*` from `example.com` will have all subrequests with the header:
+When no Worker subrequest is triggered, `cf-connecting-ip` reflects the client's IP address and the `x-real-ip` header is stripped.
 
-    `CF-Worker`: `example.com`
+</div>
+</details>
 
-    The intended purpose of this header is to provide a means for recipients (for example, origins, load balancers, other Workers) to recognize, filter, and route traffic generated by Workers on specific zones.
+<details>
+<summary>CF-Worker</summary>
+<div>
 
-    <Aside type="note">
+Added to all Worker subrequests sent via `fetch()`. Set to the name of the zone which owns the Worker making the subrequest. For example, a Worker script on route for `foo.example.com/*` from `example.com` will have all subrequests with the header:
 
-    When configuring Cloudflare Firewall Rules, do not match on this header. Firewall Rules are applied before Cloudflare adds the `CF-Worker` header. Instead, use the `cf.worker.upstream_zone`(https://tinyurl.com/2wx4senh) dynamic field, which contains the same value and exists for the same purpose.
+`CF-Worker`: `example.com`
 
-    </Aside>
+The intended purpose of this header is to provide a means for recipients (for example, origins, load balancers, other Workers) to recognize, filter, and route traffic generated by Workers on specific zones.
 
-* `CF-EW-Via`: Used for loop detection, similar to the `CDN-Loop` [header](https://blog.cloudflare.com/preventing-request-loops-using-cdn-loop/).
+<Aside type="note">
+
+When configuring Cloudflare Firewall Rules, do not match on this header. Firewall Rules are applied before Cloudflare adds the `CF-Worker` header. Instead, use the `cf.worker.upstream_zone`(https://tinyurl.com/2wx4senh) dynamic field, which contains the same value and exists for the same purpose.
+
+</Aside>
+
+</div>
+</details>
+
+<details>
+<summary>CF-EW-Via</summary>
+<div>
+
+Used for loop detection, similar to the `CDN-Loop` [header](https://blog.cloudflare.com/preventing-request-loops-using-cdn-loop/).
+
+</div>
+</details>

products/workers/src/content/runtime-apis/web-standards.md

@@ -1,6 +1,5 @@
 ---
 title: Web standards
-order: 0
 pcx-content-type: configuration
 ---