Fix busted links sep 17 (FusionAuth#3277)

* removing reference to twilio segment guide because it is not live yet. Here is the PR: FusionAuth#3229

* fix busted links

astro/src/content/blog/announcing-fusionauth-1-53.mdx

@@ -39,7 +39,7 @@ Version 1.53.0 fixes this problem by adding a webhook event log. Now you can go
 
 ## All the Rest
 
-There's more! We're updating to Java 21, we've spent a lot of time optimizing FusionAuth for performance, and miscellaneous bug fixes as well. You can get all of the details about this and much more in our [Release Notes](docs/release-notes/).
+There's more! We're updating to Java 21, we've spent a lot of time optimizing FusionAuth for performance, and miscellaneous bug fixes as well. You can get all of the details about this and much more in our [Release Notes](/docs/release-notes/).
 
 If you're not using FusionAuth, why not? We've made it easier than ever to kick the tires. Just [choose a plan](/pricing) and enter your email. There's no credit card required to get your trial started.
 

astro/src/content/blog/identity-business-value.mdx

@@ -19,7 +19,7 @@ In the early days of desktop applications, there wasn't much need to consider wh
 
 ## The Rise of Single Sign-On
 
-[Single Sign-On (SSO)](/articles/authentication/how-sso-works) has roots going back to the 90s. In these early days, SSO gained traction primarily in large enterprise environments with thousands of employees. However, it wasn't until the early 2010s that cloud implementations of SSO became widespread. Even then, SSO wasn't used for niche forums or simple websites; instead, it was adopted by large technology companies like Facebook, Google, and Microsoft. SSO allowed these companies to connect constellations of services behind a single, convenient sign-on experience. This significantly [enhanced user convenience](/articles/security/sso-ux/articles/security/sso-ux) by allowing one set of login credentials to access numerous services and improved security by reducing the number of passwords customers need to remember and manage.
+[Single Sign-On (SSO)](/articles/authentication/how-sso-works) has roots going back to the 90s. In these early days, SSO gained traction primarily in large enterprise environments with thousands of employees. However, it wasn't until the early 2010s that cloud implementations of SSO became widespread. Even then, SSO wasn't used for niche forums or simple websites; instead, it was adopted by large technology companies like Facebook, Google, and Microsoft. SSO allowed these companies to connect constellations of services behind a single, convenient sign-on experience. This significantly [enhanced user convenience](/articles/security/sso-ux) by allowing one set of login credentials to access numerous services and improved security by reducing the number of passwords customers need to remember and manage.
 
 Why is the rise of SSO important? It marked an inflection point in what Identity meant and what it could be. Identity was transforming from merely verifying who you are to enabling companies to understand who you are. This transformation ushered in a modern notion of the business value inherent in Identity.
 

astro/src/content/docs/apis/_webhook-event-log-response-body-base.mdx

@@ -13,7 +13,7 @@ import WebhookAttemptLogResponseBodyBase from 'src/content/docs/apis/_webhook-at
     An object that can hold additional details of a webhook event log.
   </APIField>
   <APIField name={ props.base_field_name + ".event" } type="Object">
-    Contains the full event request payload. The contents vary by [event](/extend/events-and-webhooks/events) type.
+    Contains the full event request payload. The contents vary by [event](/docs/extend/events-and-webhooks/events) type.
   </APIField>
   <APIField name={ props.base_field_name + ".eventResult" } type="String">
     The overall result of a [transactional](/docs/extend/events-and-webhooks/events#transaction-compatibility) event. Possible values are:

astro/src/content/docs/lifecycle/migrate-users/offboard.mdx

@@ -26,7 +26,7 @@ To learn about authentication migration in general, please see the [generic migr
 FusionAuth might also have a specific guide on migrating from the service you want to migrate to, listed [here](/docs/lifecycle/migrate-users/provider-specific/). If so, check the steps in the guide to see if there are any important differences between the two services that you need to plan for.
 
 <Aside type='note'>
-For integrating FusionAuth data with complementary services, such as exporting to a customer data warehouse with [Twilio Segment](/docs/extend/examples/twilio-segment) or using a monitoring service like [Prometheus](/docs/operate/secure-and-monitor/prometheus) or [Elastic](/docs/operate/secure-and-monitor/elastic), please see those guides.
+For integrating FusionAuth data with complementary services, such as using a monitoring service like [Prometheus](/docs/operate/secure-and-monitor/prometheus) or [Elastic](/docs/operate/secure-and-monitor/elastic), please see those guides.
 
 You should use different techniques, like webhooks and APIs, for sending data to such services, instead of the bulk database export discussed in this guide.
 </Aside>