diff --git a/packages/paste-website/src/assets/images/patterns/create-anchor.png b/packages/paste-website/src/assets/images/patterns/create-anchor.png
index da03b6db3c..99a2088221 100644
Binary files a/packages/paste-website/src/assets/images/patterns/create-anchor.png and b/packages/paste-website/src/assets/images/patterns/create-anchor.png differ
diff --git a/packages/paste-website/src/assets/images/patterns/notifications-alert@3x.png b/packages/paste-website/src/assets/images/patterns/notifications-alert@3x.png
index 0c5d09a183..32f0897526 100644
Binary files a/packages/paste-website/src/assets/images/patterns/notifications-alert@3x.png and b/packages/paste-website/src/assets/images/patterns/notifications-alert@3x.png differ
diff --git a/packages/paste-website/src/pages/components/alert/index.mdx b/packages/paste-website/src/pages/components/alert/index.mdx
index 6779330d32..c924e8e6a5 100644
--- a/packages/paste-website/src/pages/components/alert/index.mdx
+++ b/packages/paste-website/src/pages/components/alert/index.mdx
@@ -46,7 +46,7 @@ export const getStaticProps = async () => {
 
 <LivePreview scope={{Alert, Text}} language="jsx">
   {`<Alert variant="warning">
-    <strong>Chimamanda Ngozi Adichie:</strong> Racism should never have happened and so you don't get a cookie for reducing it.
+    <strong>Some information on this page may be out-of-date.</strong> This page was last updated at 9:00 a.m. PST. We're currently looking into this issue.
 </Alert>`}
 </LivePreview>
 
@@ -73,9 +73,9 @@ Use an Alert for one of these types of information:
 
 ### Accessibility
 
-- Pass in `role="alert"` or `role="status"` through [props](#props). Otherwise, the default role is `status` for neutral alerts and `alert` for warning and error alerts.
-- Screen readers announce error and warning alert text immediately. Alerts that persist across multiple pages announce themselves repeatedly which may become annoying. Consider making alerts in these cases dismissible.
-- Show an alert only when it's needed. Assistive technologies will be able to read a visually hidden element. Don't visually hide an alert and then make it visible through client-side code.
+- Pass in `role="alert"` or `role="status"` through [props](#props). Otherwise, the default role is `status` for neutral Alerts and `alert` for warning and error Alerts.
+- Screen readers announce error and warning Alert text immediately. Alerts that persist across multiple pages announce themselves repeatedly which may become annoying. Consider making Alerts in these cases dismissible.
+- Show an Alert only when it's needed. Assistive technologies will be able to read a visually hidden element. Don't visually hide an Alert and then make it visible through client-side code.
 
 Alert uses multiple methods to indicate type.
 
@@ -86,24 +86,22 @@ Alert uses multiple methods to indicate type.
 
 <Box marginBottom="space30">
   <Alert variant="neutral">
-    <strong>Martin Luther King, Jr.:</strong> We may have all come on different ships, but we’re in the same boat now.
+    <strong>Set up your contact preferences.</strong> You can now set up your contact preferences on your dashboard. <Anchor href="#">Go to contact preferences</Anchor>
   </Alert>
 </Box>
 <Box marginBottom="space30">
   <Alert variant="warning">
-    <strong>James Baldwin:</strong> Love takes off masks that we fear we cannot live without and know we cannot live
-    within.
+    <strong>Some information on this page may be out-of-date.</strong> This page was last updated at 9:00 a.m. PST. We're currently looking into this issue.
   </Alert>
 </Box>
 <Box marginBottom="space30">
   <Alert variant="error">
-    <strong>Audre Lorde:</strong> It is not our differences that divide us. It is our inability to recognize, accept,
-    and celebrate those differences.
+    <strong>Please update your billing information or we'll suspend your account on March 2.</strong> We couldn't renew your subscription with the information we currently have. <Anchor href="#">Update billing information</Anchor>
   </Alert>
 </Box>
 <Box marginBottom="space70">
-  <Alert onDismiss={() => alert('dismissed')} variant="warning">
-    <strong>Toni Morrison:</strong> You wanna fly, you got to give up the shit that weighs you down.
+  <Alert onDismiss={() => alert('dismissed')} variant="neutral">
+    <strong>Set up your contact preferences.</strong> You can now set up your contact preferences on your dashboard. <Anchor href="#">Go to contact preferences</Anchor>
   </Alert>
 </Box>
 
@@ -113,7 +111,7 @@ Use a neutral Alert to notify a user of a change that's relevant for them to ach
 
 In most cases, a neutral Alert should be dismissible (_i.e._, have a close button) and should be assigned `role="status"`.
 
-You may use [the Text primitive](/primitives/text) as a child of Alert, but if you do, be sure to pass `color="inherit"` for neutral alerts.
+You may use the [Text primitive](/primitives/text) as a child of Alert, but if you do, be sure to pass `color="inherit"` for neutral Alerts.
 
 <LivePreview scope={{Alert, Text, Anchor}} language="jsx">
   {`<Alert variant="neutral">
@@ -129,23 +127,23 @@ A warning Alert should provide explain the possible issue, what to do, and what
 
 Be cautious about using a warning Alert because they can be stressful for a user to see. In most cases, a warning Alert should be assigned `role="alert"`.
 
-You may use [the Text primitive](/primitives/text) as a child of Alert, but if you do, be sure to pass `color="inherit"` for warning alerts.
+You may use the [Text primitive](/primitives/text) as a child of Alert, but if you do, be sure to pass `color="inherit"` for warning Alerts.
 
 <LivePreview scope={{Alert, Text}} language="jsx">
   {`<Alert variant="warning">
-    <strong>Some information on this page may be out-of-date.</strong> This page was last updated at 9:00 AM PST. We're currently looking into this issue.
+    <strong>Some information on this page may be out-of-date.</strong> This page was last updated at 9:00 a.m. PST. We're currently looking into this issue.
 </Alert>`}
 </LivePreview>
 
 ### Error
 
-Use an error Alert to help a user understand a critical issue at the system level, like site-wide service disruptions, active incidents, or expired billing information. When possible, provide a way to resolve the issue in the alert.
+Use an error Alert to help a user understand a critical issue at the system level, like site-wide service disruptions, active incidents, or expired billing information. When possible, provide a way to resolve the issue in the Alert.
 
 In most cases, error Alerts should be assigned `role="alert"`.
 
 For additional guidance on what kind of component to use, use the [Alert vs. Callout vs. Toast vs. Help Text guide](#alert-vs-callout-vs-toast-vs-help-text). For additional guidance on how to compose error messages, refer to the [error state pattern](/patterns/error-state).
 
-You may use [the Text primitive](/primitives/text) as a child of Alert, but if you do, be sure to pass `color="inherit"` for error alerts.
+You may use the [Text primitive](/primitives/text) as a child of Alert, but if you do, be sure to pass `color="inherit"` for error Alerts.
 
 <LivePreview scope={{Alert, Text, Anchor}} language="jsx">
   {`<Alert variant="error">
@@ -155,15 +153,15 @@ You may use [the Text primitive](/primitives/text) as a child of Alert, but if y
 
 ### Dismissible
 
-Add a close button to the alert if it doesn't communicate a persistent status of the system or the account. If you make an alert dismissible, provide another way for the user to retrieve the alert information.
+Make the Alert dismissible if it doesn't communicate a persistent status of the system or the account. If you make an Alert dismissible, provide another way for the user to retrieve the alert information.
 
-Don't add a close button to the alert if all these conditions are true:
+Don't make it dismissible if all these conditions are true:
 
-- The alert communicates a persistent status of the system or the account.
-- The information is relevant to the user's goals on the page(s) the alert is on.
-- The user wouldn't be able to access the information in the alert if it were closed.
+- The Alert communicates a persistent status of the system or the account.
+- The information is relevant to the user's goals on the page(s) the Alert is on.
+- The user wouldn't be able to access the information in the Alert if it were closed.
 
-Keep in mind that the longer an alert is present, the more it starts looking like part of the page and loses its interruptive intent. This might make users start to ignore important alert information.
+Keep in mind that the longer an Alert is present, the more it starts looking like part of the page and loses its interruptive intent. This might make users start to ignore important Alert information.
 
 <LivePreview scope={{Alert, Text, Anchor}} language="jsx">
   {`<Alert onDismiss={() => alert('dismissed')} variant="neutral">
@@ -187,7 +185,7 @@ For an `error` variant, for example, set the `i18nErrorLabel` prop.
 
 ## Composition notes
 
-Keep content brief by placing only the highest priority information in an Alert. A good rule of thumb is to keep text to a single line in a desktop-sized container, or [limit it to 90 characters](https://practicaltypography.com/responsive-web-design.html).
+Keep content brief by placing only the highest priority information in an Alert. Generally try to [limit content to 90 characters](https://practicaltypography.com/responsive-web-design.html).
 
 Compose an Alert with:
 
@@ -213,7 +211,7 @@ Alert
 [Toast](/components/toast)
 
 - Toasts communicate brief, easily comprehended messages.
-- Toasts generally result from a user action.
+- Toasts result from a user action.
 - If the message is contextual or specific to a particular part of a page, consider Help Text or a Callout.
 - Do not use a Toast if the message is longer than two sentences (~140 characters). Use a Callout instead.
 - Do not use a Toast if there is more than one anchor or button. Use a Callout instead.
@@ -234,13 +232,13 @@ In general, the persistence and behavior on scroll of an Alert should match the
 <DoDont>
   <Do
     title="Do"
-    body="Use only one Alert per page. Use two Alerts only if absolutely necessary and if the Alerts are placed in different containers. Be sure to add 0.5rem spacing if using two Alerts."
+    body="Use only 1 Alert per page. Use 2 Alerts only if absolutely necessary and if the Alerts are placed in different containers. Add space30 spacing if using 2 Alerts."
   >
     <Alert variant="error">
-      Your account balance is low and your credit card has expired. As a result we have suspended your account
+      Your account balance is low and your credit card has expired. As a result, we have suspended your account.
     </Alert>
   </Do>
-  <Dont title="Don't" body="Don't use more than two Alerts per page.">
+  <Dont title="Don't" body="Don't use more than 2 Alerts per page.">
     <Alert variant="error">Your credit card has expired</Alert>
     <Alert variant="warning">Your account balance is low</Alert>
     <Alert variant="error">Your account is suspended</Alert>
@@ -250,16 +248,16 @@ In general, the persistence and behavior on scroll of an Alert should match the
 <DoDont>
   <Do
     title="Do"
-    body="Place global Alerts at the top of the page. Place all other Alerts at the top of the container it relates to beneath the heading."
+    body="Place global or page-level Alerts at the top of the page. Place all other Alerts at the top of the container it relates to."
   >
     <Box padding="space40">
       <Card>
-        <Heading as="h2" variant="heading20">
-          Section Heading
-        </Heading>
         <Box marginBottom="space70">
           <Alert variant="error">There was a problem below</Alert>
         </Box>
+        <Heading as="h2" variant="heading20">
+          Section Heading
+        </Heading>
         <Paragraph>Please fill in the details below...</Paragraph>
       </Card>
     </Box>
@@ -279,13 +277,13 @@ In general, the persistence and behavior on scroll of an Alert should match the
 <DoDont>
   <Do
     title="Do"
-    body="Use anchors to link to more information that may be helpful for users to resolve or clarify an Alert message."
+    body="Use Anchors to link to more information that may be helpful for users to resolve or clarify an Alert message."
   >
     <Alert variant="neutral">
       A call to action <Anchor href="#">Learn more</Anchor>
     </Alert>
   </Do>
-  <Dont title="Don't" body="Avoid using buttons in Alerts unless it triggers an action.">
+  <Dont title="Don't" body="Avoid using Buttons in Alerts unless it triggers an action.">
     <Alert variant="neutral">
       A call to action{' '}
       <Button size="small" variant="primary">
diff --git a/packages/paste-website/src/pages/components/callout/index.mdx b/packages/paste-website/src/pages/components/callout/index.mdx
index 42d469b747..7bb8642f4a 100644
--- a/packages/paste-website/src/pages/components/callout/index.mdx
+++ b/packages/paste-website/src/pages/components/callout/index.mdx
@@ -47,41 +47,43 @@ export const getStaticProps = async () => {
 
 ### About Callout
 
-Use a Callout to highlight important information on a page or in a page section. Callouts can result from user action, but don’t have to. Do not use a Callouts to tell users about a system-level issue; use an [Alert](/components/alert) instead. Do not use a Callout to convey brief, low-complexity information; use a [Toast](/components/toast) instead. For additional guidance on what kind of component to use, use the [Alert vs. Callout vs. Toast vs. Help Text guide](#alert-vs-callout-vs-toast-vs-help-text).
+Use a Callout to highlight important information on a page. Callouts are less restrictive than Alerts or Toasts—they can result from user action, but don’t have to.
+
+Do not use a Callout to tell users about a system-level issue; use an [Alert](/components/alert) instead. For additional guidance on what kind of component to use, reference the [Alert vs. Callout vs. Toast vs. Help Text guide](#alert-vs-callout-vs-toast-vs-help-text).
 
 ### Accessibility
 
-We recommend Callouts have a CalloutHeading so that the information is easier to navigate to for people who use screen readers. The CalloutHeading's level should be set appropriately with the `as` prop. It is important to not skip one or more heading levels as it is common for screen readers to build an outline of the page and assist users as they navigate a page.
+Callouts should have a `CalloutHeading` so that the information is easier to navigate to for people who use screen readers. The `CalloutHeading`'s level should be set appropriately with the `as` prop. It is important to not skip one or more heading levels as it is common for screen readers to build an outline of the page and assist users as they navigate a page.
 
 ## Examples
 
 There are five variants of Callouts: `neutral`, `success`, `warning`, `error`, and `new`. Each variant includes an icon.
 
-Each variant includes an icon. To internationalize the icon label for a variant, simply pass the `i18nLabel` prop.
+To internationalize the icon label for a variant, pass the `i18nLabel` prop.
 
 ### Neutral Callout
 
-Use a neutral Callout to communicate relevant information to the page or flow. The information is often static.
+Use a neutral Callout to communicate relevant information to the page or flow. This information is often static.
 
 <LivePreview scope={{ Callout, CalloutHeading, CalloutText }} language="jsx">
   {`
   <Callout variant='neutral'>
-    <CalloutHeading as="h2">Neutral Callout</CalloutHeading>
-    <CalloutText>This is some information you need to know.</CalloutText>
+    <CalloutHeading as="h2">Finding your category ID</CalloutHeading>
+    <CalloutText>On your dashboard, look for the relevant "Category ID". It will contain up to five alphanumeric characters.</CalloutText>
   </Callout>`}
 </LivePreview>
 
 ### Success Callout
 
-Use a success Callout to communicate that the desired outcome was achieved. A success Callout can be appropriate when the outcome is relevant to a particular part of the page, or when additional information or context needs to be provided.
+Use a success Callout to communicate that the desired outcome was achieved. A success Callout can be appropriate when the outcome is relevant to a specific part of the page, or when additional information or context needs to be provided.
 
-When composing a success Callout, avoid using the word "successfully"—it's redundant.
+When composing a success Callout, avoid using the word "successfully" since it's redundant.
 
 <LivePreview scope={{ Callout, CalloutHeading, CalloutText }} language="jsx">
   {`
   <Callout variant='success'>
-    <CalloutHeading as="h2">Success Callout</CalloutHeading>
-    <CalloutText>This is some information you need to know.</CalloutText>
+    <CalloutHeading as="h2">Recommended action</CalloutHeading>
+    <CalloutText>Make sure you have permission first. Only send messages to mobile users who have provided consent (opted-in) to receive messages from you.</CalloutText>
   </Callout>`}
 </LivePreview>
 
@@ -94,8 +96,8 @@ A warning Callout should should explain the possible issue, what to do, and what
 <LivePreview scope={{ Callout, CalloutHeading, CalloutText }} language="jsx">
   {`
   <Callout variant='warning'>
-    <CalloutHeading as="h2">Warning Callout</CalloutHeading>
-    <CalloutText>This is some information you need to know.</CalloutText>
+    <CalloutHeading as="h2">Permission settings will change in 30 days.</CalloutHeading>
+    <CalloutText>Update your permission settings now to avoid any delays or issues accessing your accounts.</CalloutText>
   </Callout>`}
 </LivePreview>
 
@@ -106,8 +108,8 @@ Use an error Callout to communicate errors for a particular section of a page, o
 <LivePreview scope={{ Callout, CalloutHeading, CalloutText }} language="jsx">
   {`
   <Callout variant='error'>
-    <CalloutHeading as="h2">Error Callout</CalloutHeading>
-    <CalloutText>This is some information you need to know.</CalloutText>
+    <CalloutHeading as="h2">Missing values</CalloutHeading>
+    <CalloutText>Please fill out the "Street address" field.</CalloutText>
   </Callout>`}
 </LivePreview>
 
@@ -118,18 +120,19 @@ Use a new Callout to spotlight a recent addition or update.
 <LivePreview scope={{ Callout, CalloutHeading, CalloutText }} language="jsx">
   {`
   <Callout variant='new'>
-    <CalloutHeading as="h2">New Callout</CalloutHeading>
-    <CalloutText>This is some information you need to know.</CalloutText>
+    <CalloutHeading as="h2">Early access to AI features</CalloutHeading>
+    <CalloutText>You have early access to deliverability scores, Intelligent Discovery Assistant, and intelligent alerts. Try out these new features, and get personalized alerts and recommendations for your account.</CalloutText>
   </Callout>`}
 </LivePreview>
 
 ### Dismissible Callout
 
+Make a Callout dismissible with the `onDismiss` prop if it doesn't communicate a persistent status of the system or the account, or you provide another way for the user to access the information.
+
 <LivePreview scope={{ Callout, CalloutHeading, CalloutText }} language="jsx">
   {`
   <Callout variant='new' onDismiss={() => alert("dismissed")}>
-    <CalloutHeading as="h2">Dismissible Callout</CalloutHeading>
-    <CalloutText>This callout can be provided an onDismiss prop to allow for dismissible functionality.</CalloutText>
+    <CalloutText>Changes to conference insights settings apply only to conferences created in the past 30 days.</CalloutText>
   </Callout>`}
 </LivePreview>
 
@@ -175,9 +178,9 @@ Callouts can be inline with text, so use the `marginY` prop to add a vertical ma
 
 Compose a Callout with:
 
-- **Title (optional).** The title should be concise and convey the essense of the issue.
-- **Body text.** Use the default text style. Do not repeat information contained in a title. If the user needs to take action on another page, or more information would be helpful, include an [Anchor](/components/anchor).
-- **Full punctuation.** Use periods after full sentences. Avoid using exclamation points.
+- **Heading (optional).** The heading should be concise and convey the essence of the issue.
+- **Body text.** Use the default text style. Do not repeat information contained in the heading. If the user needs to take action on another page, or more information would be helpful, include an [Anchor](/components/anchor).
+- **Full punctuation.** Use periods after full sentences.
 
 ### Alert vs. Callout vs. Toast vs. Help Text
 
@@ -195,10 +198,10 @@ Callout
 Toast
 
 - Toasts communicate brief, easily comprehended messages.
-- Toasts generally result from a user action.
+- Toasts result from a user action.
 - If the message is contextual or specific to a particular part of a page, consider Help Text or a Callout.
 - Do not use a Toast if the message is longer than two sentences (~140 characters). Use a Callout instead.
-- Do not use a Toast if there is more than one anchor or button. Use a Callout instead.
+- Do not use a Toast if there is more than one Anchor or Button. Use a Callout instead.
 
 Help Text
 
diff --git a/packages/paste-website/src/pages/components/page-header/index.mdx b/packages/paste-website/src/pages/components/page-header/index.mdx
index a5223c8c04..e3cd04c6f2 100644
--- a/packages/paste-website/src/pages/components/page-header/index.mdx
+++ b/packages/paste-website/src/pages/components/page-header/index.mdx
@@ -107,7 +107,7 @@ Here’s what the component layout looks like with all its bits and pieces:
 
 <Callout variant='neutral' marginY="space60">
     <CalloutHeading as="h2">Using Alerts with Page Headers</CalloutHeading>
-    <CalloutText>There are times when you’ll need to display an <Anchor href="/components/alert">Alert</Anchor> at the top of a page to communicate an important message to the user. Alerts should not be children of the Page Header component. If the Alert communicates a platform-level message, place it above the Page Header. If the Alert communicates a page-level message, place it below the Page Header.</CalloutText>
+    <CalloutText>There are times when you’ll need to display an <Anchor href="/components/alert">Alert</Anchor> at the top of a page to communicate an important message to the user. Place Alerts above the Page Header. Alerts should not be children of the Page Header component. </CalloutText>
 </Callout>
 
 Much of the Paste Page Header component was inspired by the wonderful work of Github’s Primer Design system and [their own Page Header](https://primer.style/components/page-header) API and documentation.
@@ -126,7 +126,7 @@ Page Header has no inherent accessibility concerns. However, there will likely b
 
 The Page Header can be composed to fit the needs of your page. Only include necessary components.
 
-Default Page Headers should have `space-130` clearspace above them. Place platform-level Alerts above this clearspace.
+Default Page Headers should have `space-130` clearspace above them. Place Alerts above this clearspace.
 
 <LivePreview scope={{PageHeader, PageHeaderKeyword, PageHeaderSetting, Breadcrumb, BreadcrumbItem, Badge, NewIcon, ArrowForwardIcon, PageHeaderActions, PageHeaderHeading, PageHeaderDetails, ButtonGroup, Button, PageHeaderParagraph, PageHeaderInPageNavigation, InPageNavigation, InPageNavigationItem}} language="jsx" noInline>
   {defaultPageHeaderExample}
diff --git a/packages/paste-website/src/pages/patterns/notifications-and-feedback/index.mdx b/packages/paste-website/src/pages/patterns/notifications-and-feedback/index.mdx
index 1ef4b8cf0f..aed7263a34 100644
--- a/packages/paste-website/src/pages/patterns/notifications-and-feedback/index.mdx
+++ b/packages/paste-website/src/pages/patterns/notifications-and-feedback/index.mdx
@@ -70,7 +70,7 @@ Each notification or feedback pattern uses one or more of these components.
       </Card>
       <Card>
         <Heading as="h3" variant="heading40" marginBottom="space0">
-          <Anchor href="/components/toast">Toast</Anchor>
+          <Anchor href="/components/callout">Callout</Anchor>
         </Heading>
       </Card>
     </Stack>
@@ -79,7 +79,7 @@ Each notification or feedback pattern uses one or more of these components.
     <Stack orientation="vertical" spacing="space50">
       <Card>
         <Heading as="h3" variant="heading40" marginBottom="space0">
-          <Anchor href="/components/input/#input-with-inline-error">Inline error on form fields</Anchor>
+          <Anchor href="/components/help-text">Help Text</Anchor>
         </Heading>
       </Card>
       <Card>
@@ -90,32 +90,40 @@ Each notification or feedback pattern uses one or more of these components.
     </Stack>
   </Column>
   <Column>
-    <Card>
-      <Heading as="h3" variant="heading40">
-        Component composition
-      </Heading>
-      <Paragraph marginBottom="space0">
-        Create a composition with <Anchor href="/components/card">Card</Anchor>,{' '}
-        <Anchor href="/components/heading">Heading</Anchor>, and <Anchor href="/components/paragraph">Paragraph</Anchor>{' '}
-        for in-page messaging.
-      </Paragraph>
-    </Card>
+    <Stack orientation="vertical" spacing="space50">
+      <Card>
+        <Heading as="h3" variant="heading40" marginBottom="space0">
+          <Anchor href="/components/toast">Toast</Anchor>
+        </Heading>
+      </Card>
+      <Card>
+        <Heading as="h3" variant="heading40">
+          Component composition
+        </Heading>
+        <Paragraph marginBottom="space0">
+          Create a composition with <Anchor href="/components/card">Card</Anchor>,{' '}
+          <Anchor href="/components/heading">Heading</Anchor>, and <Anchor href="/components/paragraph">Paragraph</Anchor>{' '}
+          for in-page messaging.
+        </Paragraph>
+      </Card>
+    </Stack>
   </Column>
 </Grid>
 
 ```jsx
 // import all components for Notification and feedback patterns
 
-import {​ Alert } from "@twilio-paste/core/alert;
+import {​ Alert } from "@twilio-paste/core/alert";
+import { Callout, CalloutHeading, CalloutText } from '@twilio-paste/core/callout';
 import { Toast } from "@twilio-paste/core/toast";
 import { Label } from "@twilio-paste/core/label";
 import { Input } from "@twilio-paste/core/input";
-import { HelpText } from "@twilio-paste/core/help-text;
+import { HelpText } from "@twilio-paste/core/help-text";
 import {​ Button } from "@twilio-paste/core/button";
 import { Modal, ModalBody, ModalFooter, ModalFooterActions, ModalHeader, ModalHeading } from "@twilio-paste/core/modal";
 import {​ Card } from "@twilio-paste/core/card";
 import {​ Heading } from "@twilio-paste/core/heading";
-import {​ Paragraph } from "@twilio-paste/core/paragraph;
+import {​ Paragraph } from "@twilio-paste/core/paragraph";
 ```
 
 ## Usage
@@ -124,7 +132,7 @@ import {​ Paragraph } from "@twilio-paste/core/paragraph;
 
 Pairing thoughtful content writing with the appropriate UI elements can help you establish trust with customers by notifying them of relevant information at just the right time. Use these patterns only when the user **needs** to be notified.
 
-In general, notifications should close when a user leaves the page. A notification should follow a user through the product only in the most critical cases, like an alert informing a customer that their paid account won’t renew soon because of expired billing information.
+In general, notifications should close when a user leaves the page. A notification should follow a user through the product only in the most critical cases, like an Alert informing a customer that their paid account won’t renew soon because of expired billing information.
 
 Too many notifications that appear for too long may lead to alert fatigue, causing users to ignore important information.
 
@@ -154,30 +162,21 @@ Notifications and feedback can come in 4 variants:
 
 Give users enough time to read a notification message, make a decision, and act on their decision. Users’ reading speeds, vision levels, literacy levels, dexterity, and familiarity with Twilio products can all affect how much time they’ll need to interact with a notification.
 
-Visit the [Alert](/components/alert), [Modal](/components/modal), [Form element](/components/input), and [Toast](/components/toast) pages for more specific guidelines on how to implement each component accessibly.
+Visit the [Alert](/components/alert), [Modal](/components/modal), [Form](/components/form), and [Toast](/components/toast) pages for more specific guidelines on how to implement each component accessibly.
 
 ## Notification and feedback levels
 
 ### System-initiated notifications
 
-To communicate information from the system that isn't triggered by a user action, use an **[alert](/components/alert)**, especially for high-priority or time-sensitive changes to the system.
-
-<ResponsiveImage src={NotificationsAlertImage} alt="Screen with alert informing users of a server error" />
+To communicate information from the system that isn't triggered by a user action, use an **[Alert](/components/alert)**, especially for high-priority or time-sensitive changes to the system.
 
-<Box marginBottom="space80">
-  <Disclosure variant="contained">
-    <DisclosureHeading as="h4" variant="heading50">
-      Show live example
-    </DisclosureHeading>
-    <DisclosureContent>TBD</DisclosureContent>
-  </Disclosure>
-</Box>
+<ResponsiveImage src={NotificationsAlertImage} alt="Screen with Alert informing users of a server error" />
 
 ### Feedback indicators
 
-To communicate feedback on a user action, use a **[toast](/components/toast)**, **[modal](/components/modal)**, **inline messaging**, and/or **in-page messaging** (e.g., full-page confirmation).
+To communicate feedback on a user action, use a **[Toast](/components/toast)**, **[Callout](/components/callout)**, **[Modal](/components/modal)**, **[Help Text](/components/help-text)**, and/or **in-page messaging** (e.g., full-page confirmation).
 
-While you’ll only need one type of feedback indicator in most cases, pairing 2 feedback indicators can help give users more clarity in completing a complex flow. For example, when a user submits a long form with errors, you can show an error toast that lets users know they need to fix a form, while also showing inline errors on each incorrect field.
+While you’ll only need one type of feedback indicator in most cases, pairing 2 feedback indicators can help give users more clarity in completing a complex flow. For example, when a user submits a long form with an error, you can show an error Toast that lets users know they need to fix a form, while also showing error Help Text on the incorrect field.
 
 #### Standard feedback indicator (Toast)
 
@@ -185,26 +184,13 @@ Use a Toast when
 
 - You’re communicating a direct response to a user action. Example: "asset.jpg" successfully added.
 - You're providing only one link or button to help a user continue a flow.
-- There’s no other way for a user to immediately know that their action was acknowledged. For example, a Toast may not be needed when a modal closes after a user presses “Save” in it. The modal dismissal may sufficiently communicate that the information in the modal was saved, without needing further messaging.
+- There’s no other way for a user to immediately know that their action was acknowledged. For example, a Toast isn't needed when a Modal closes after a user presses “Save” in it. The dismissal of the Modal can communicate that the information was saved, without needing further messaging.
 
 <ResponsiveImage
   src={NotificationsToastImage}
-  alt="Screen with toast confirming a password reset email has been sent"
+  alt="Screen with Toast confirming a password reset email has been sent"
 />
 
-<Callout variant="neutral" marginY="space70">
-  <CalloutHeading as="h5">Toasts in Flex and SendGrid?</CalloutHeading>
-  <CalloutText>
-    While the recommendation is to migrate to Paste Toast components to acknowledge user actions, Flex and SendGrid
-    currently use banners for this purpose.
-  </CalloutText>
-  <CalloutText>
-    These banners generally exist at the top of the page, especially for page-level actions, with a limit of 3 per page.
-    The oldest one is removed when a new one displays. In Flex, banners may be placed at the top of a specific section
-    where the action was taken.
-  </CalloutText>
-</Callout>
-
 #### Interruptive feedback indicator (Modal)
 
 Use a Modal when
@@ -215,37 +201,18 @@ Use a Modal when
 
 <ResponsiveImage src={NotificationsModalImage} alt="Modal congratulating a user at the end of a Modal flow" />
 
-<Box marginBottom="space80">
-  <Disclosure variant="contained">
-    <DisclosureHeading as="h5" variant="heading50">
-      Show live example
-    </DisclosureHeading>
-    <DisclosureContent>TBD</DisclosureContent>
-  </Disclosure>
-</Box>
+#### Contextual feedback indicator (Help Text)
 
-#### Contextual feedback indicator (Inline messaging)
-
-Use contextual, inline messaging (e.g., inline errors on form fields) when
+Use Help Text when
 
 - You’re communicating a direct response to a user action.
 - You’re providing links or buttons that are contextual to a UI element and help a user continue a flow.
-- You’re communicating dynamically changing content, like a progress bar.
 
 <ResponsiveImage src={NotificationsInlineMessagingImage} alt="Screen with inline error with anchor on a form field" />
 
-<Box marginBottom="space80">
-  <Disclosure variant="contained">
-    <DisclosureHeading as="h5" variant="heading50">
-      Show live example
-    </DisclosureHeading>
-    <DisclosureContent>TBD</DisclosureContent>
-  </Disclosure>
-</Box>
-
 #### High-emotion feedback indicator (In-page messaging)
 
-Use in-page messaging (e.g., full-page confirmation composition) when
+Use in-page messaging (e.g., full-page confirmation) when
 
 - You’re communicating a direct response to a _high-emotion_ user action or flow.
 - You’re providing information that a user might want to copy, screenshot, or save, like a confirmation number or invoice details.
@@ -255,29 +222,6 @@ Use in-page messaging (e.g., full-page confirmation composition) when
   alt="Full-page congratulations message on setting up a Twilio Messaging Service with SIDs to copy"
 />
 
-<Box marginBottom="space80">
-  <Disclosure variant="contained">
-    <DisclosureHeading as="h5" variant="heading50">
-      Show live example
-    </DisclosureHeading>
-    <DisclosureContent>TBD</DisclosureContent>
-  </Disclosure>
-</Box>
-
-## Starter kits
-
-### CodeSandbox
-
-Coming soon
-
-### Figma
-
-Coming soon
-
-## Related discussions
-
-- [Thoughts on expanded size variants for Toast](https://github.com/twilio-labs/paste/discussions/834)
-
 </content>
 
 </contentwrapper>