Fix typos, duplicate anchor, missing quotes, broken links; archive bbs-encryption-keys and routing-keepalive [ai-assisted]

anita-flegg · anita-flegg · commit b162610374f5 · 2026-03-06T11:03:51.000-08:00
Made-with: Cursor
diff --git a/archive/bbs-encryption-keys.html.md.erb b/archive/bbs-encryption-keys.html.md.erb
diff --git a/archive/routing-keepalive.html.md.erb b/archive/routing-keepalive.html.md.erb
@@ -23,7 +23,7 @@ The Gorouter has been hardcoded with a limit of 100 idle connections per back en
 
 ## <a id="app-idle-timeout"></a> Considerations for apps when keep alive connections are activated
 
-When keep alive connections with back ends is activated, the Gorouter must be reponsible for closing connections.
+When keep alive connections with back ends is activated, the Gorouter must be responsible for closing connections.
 If an app instance closes a connection at the exact same time that the Gorouter sends a new request using that connection, the request fails, and the
 client receives an HTTP 502 error.
 
diff --git a/configuring-delayed-job-priorities.html.md.erb b/configuring-delayed-job-priorities.html.md.erb
@@ -8,12 +8,12 @@ You can change the priority of delayed jobs with the Cloud Controller in <%= var
 
 ## <a id='overview'></a> Cloud Controller and job priority
 
-<%= vars.app_runtime_first %> creates delayed jobs as it performs certain asynchronous actions, such as `DELETE v3/buildbacks/[GUID]`. These jobs are
+<%= vars.app_runtime_first %> creates delayed jobs as it performs certain asynchronous actions, such as `DELETE v3/buildpacks/[GUID]`. These jobs are
 processed asynchronously by multiple worker processes.
 
 By default, all jobs have the same priority of `0`. Job priorities of higher numerical values are lower than job priorities of lower numerical values.
 Conversely, job priorities of negative numerical values are higher than job priorities of positive numerical values. For example, the Cloud Controller
-schedules a job with a priority of `-1` before a job with a priority of `0`, and schedules a job with a priority of `1` before a job with a priority of `0`.
+schedules a job with a priority of `-1` before a job with a priority of `0`, and schedules a job with a priority of `1` after a job with a priority of `0`.
 
 When a job fails, the Cloud Controller might reschedule the job and give it a lower priority, depending on how the job is configured. When the Cloud
 Controller reschedules a failed job and gives it a lower priority, it doubles the priority each time the job fails: first from `0` to `1`, then to `2`, then
@@ -26,7 +26,7 @@ afterward.
 
 ## <a id='delayed-jobs'></a> Delayed jobs
 
-In the logs for some Cloud Controller components, you can view a jobs that have been delayed in the `delayed_jobs` table.
+In the logs for some Cloud Controller components, you can view jobs that have been delayed in the `delayed_jobs` table.
 
 The following list contains the `display_name` of each job in the `delayed_jobs` table that you can configure with a different default priority:
 
diff --git a/distributed-tracing.html.md.erb b/distributed-tracing.html.md.erb
@@ -28,8 +28,8 @@ Every span in a trace shares this ID. The `X-B3-TraceId` header is encoded as
 * `X-B3-Spanid` - 64-bit in length and indicates the position of the current
 operation in the trace tree. The `X-B3-SpanId` header is encoded as 16
 lower-hex characters.
-* `B3` - a combination of `X-B3-Traceid` and `X-B3-Spanid` headers in the
-format: `{TraceId}-{SpanId}`
+* `B3` - combines `X-B3-Traceid`, `X-B3-Spanid`, sampling state (trace flags),
+and an optional parent span ID in the format: `{TraceId}-{SpanId}-{SamplingState}[-{ParentSpanId}]`
 
 If W3C is enabled through the `router.tracing.enable_w3c` deployment manifest property,
 GoRouter generates W3C headers for each request unless they were provided
@@ -111,5 +111,5 @@ The `X-B3-Traceid` can be used to filter logs in aggregation tools to see how th
 
 ### <a id='distributed-tracing-cli-example'></a> Analyzing Cloud Foundry CLI command requests
 
-As of the Cloud Foundry CLI version 8.12.0 and later, the CLI client automatically sets B3 headers. It will generate a single X-B3-Traceid for all API calls originiating per command and generate new X-B3-Spanid per API call.
+As of the Cloud Foundry CLI version 8.12.0 and later, the CLI client automatically sets B3 headers. It will generate a single X-B3-Traceid for all API calls originating per command and generate new X-B3-Spanid per API call.
 Users can manually set the X-B3-Traceid header by setting the `CF_B3_TRACE_ID` environment variable.
diff --git a/instance-identity.html.md.erb b/instance-identity.html.md.erb
@@ -20,7 +20,7 @@ To enable this feature in <%= vars.app_runtime_abbr %> deployments not based on
 * `diego.executor.instance_identity_ca_cert`: PEM-encoded CA certificate used to issue Instance Identity credentials.
 * `diego.executor.instance_identity_key`: PEM-encoded private key used to issue instance identity credentials.
 
-You can also install the Instance Identity CA certificate as a trusted system certificate for apps, so that app instances trust each others' Instance Identity credentials automatically. For more information about installing this CA certificate, see [Configuring Trusted System Certificates for Apps](../running/trusted-system-certificates.html).
+You can also install the Instance Identity CA certificate as a trusted system certificate for apps, so that app instances trust each others' Instance Identity credentials automatically. To do so, provide the PEM-encoded CA certificate in the `containers.trusted_ca_certificates` BOSH property on `rep` and `rep_windows` jobs for the Diego release.
 
 For information about how developers can use the Instance Identity credentials in apps on <%= vars.app_runtime_abbr %>, see [Using Instance Identity Credentials](../devguide/deploy-apps/instance-identity.html).
 
diff --git a/stack-auditor.html.md.erb b/stack-auditor.html.md.erb
@@ -224,9 +224,9 @@ If your application is .NET 6 and uses GSS, you may see the following error mess
 GSSAPI operation failed with error - Unspecified GSS failure. Minor code may provide more information (Crypto routine failure).
 </pre>
 
-There is an existing .NET issue about this failure, which is related to legacy usage of OpenSSL3. For more information, see <a href=https://github.com/dotnet/runtime/issues/67353>GSS failures in System.Net.Http.Functional.Tests on Ubuntu 22.04re</a> on GitHub. The workaround is listed <a href=https://github.com/dotnet/runtime/issues/67353#issuecomment-1085003764>on the same page</a> and involves explicitly loading the legacy provider.
+There is an existing .NET issue about this failure, which is related to legacy usage of OpenSSL3. For more information, see <a href="https://github.com/dotnet/runtime/issues/67353">GSS failures in System.Net.Http.Functional.Tests on Ubuntu 22.04</a> on GitHub. The workaround is listed <a href="https://github.com/dotnet/runtime/issues/67353#issuecomment-1085003764">on the same page</a> and involves explicitly loading the legacy provider.
 
-### <a id="dotnet-gss"></a> .NET Core apps and LDAP
+### <a id="dotnet-ldap"></a> .NET Core apps and LDAP
 
 If your application is .NET Core and using LDAP connectivity, you may see the following error message if you are using cflinuxfs4 prior to v1.45.0:
 
diff --git a/troubleshooting-router-error-responses.html.md.erb b/troubleshooting-router-error-responses.html.md.erb
@@ -407,7 +407,6 @@ The app might be overloaded, unresponsive, or unable to connect to the database.
 When all apps are experiencing 502 errors, then it could either be a platform issue. For example, a misconfiguration, or an app issue likely all apps being unable to connect to an upstream database.
 
 If the Gorouter has back end keep-alive connections activated, 502 errors can occur due to a race condition when the app instance keep alive idle timeout is less than 90 seconds.
-For more information, see [Gorouter Back End Keep-Alive Connections](../adminguide/routing-keepalive.html).
 
 For any other errors that appear in Gorouter access logs, you can analyze application logs if they need further investigation.
 
