diff --git a/src/_includes/content/functions/runtime.md b/src/_includes/content/functions/runtime.md
index 1eec66aa95..4073eaa30c 100644
--- a/src/_includes/content/functions/runtime.md
+++ b/src/_includes/content/functions/runtime.md
@@ -1,23 +1,10 @@
-On March 26, 2024, Segment is upgrading the Functions runtime environment to Node.js v18, which is the current long-term support (LTS) release.
+On March 26, 2024, Segment upgraded the Functions runtime environment to Node.js v18, which is the current long-term support (LTS) release.
 
 This upgrade keeps your runtime current with industry standards. Based on the [AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html){:target="_blank"} and [Node.js](https://nodejs.org/en/about/previous-releases){:target="_blank"} support schedule, Node.js v16 is no longer in *Maintenance LTS*. Production applications should only use releases of Node.js that are in *Active LTS* or *Maintenance LTS*.
 
-All new functions will use Node.js v18 starting March 26, 2024.
+For existing functions, this change automatically occurs as you update and deploy an existing function. Segment recommends that you check your function post-deployment to ensure everything's working. Your function may face issues due to the change in syntax between different Node.js versions and dependency compatibility.
 
-For existing functions, this change automatically occurs as you update and deploy an existing function. Segment recommends that you check your function post-deployment to ensure everything's working. Your function may face issues due to the change in sytax between different Node.js versions and dependency compatibility.
-
-<div class="premonition warning"><div class="fa fa-check-square"></div><div class="content"><p class="header">Limited time opt-out option </p><p markdown=1>
-If you need more time to prepare, you can opt out of the update before March 19, 2024. <br><br> Note that if you opt out: <br>
-- The existing functions will continue working on Node.js v16. <br>
-- You won't be able to create new functions after July 15, 2024. <br>
-- You won't be able to update existing functions after August 15, 2024. <br>
-- You won't receive future bug fixes, enhancements, and dependency updates to the functions runtime. <br><br>
-[Contact Segment](https://segment.com/help/contact/){:target="_blank"} to opt-out or with any questions. </p></div></div>
-
-
-<div class="premonition success"><div class="fa fa-check-square"></div><div class="content"><p class="header">Node.js 18 </p><p markdown=1>Segment strongly recommends updating to Node.js v18 to benefit from future runtime updates, the latest security, and performance improvements.</p></div></div>
-
-Functions do not currently support importing dependencies, but you can [contact Segment Support](https://segment.com/help/contact/){:target="_blank"} to request that one be added.
+Functions don't currently support importing dependencies, but you can [contact Segment Support](https://segment.com/help/contact/){:target="_blank"} to request that one be added.
 
 The following dependencies are installed in the function environment by default.
 
diff --git a/src/_includes/content/functions/settings.md b/src/_includes/content/functions/settings.md
index 2b11c86279..e2becaa0a5 100644
--- a/src/_includes/content/functions/settings.md
+++ b/src/_includes/content/functions/settings.md
@@ -2,15 +2,15 @@
 
 Settings allow you to pass configurable variables to your function, which is the best way to pass sensitive information such as security tokens. For example, you might use `settings` as placeholders to use information such as an API endpoint and API key. This way, you can use the same code with different settings for different purposes. When you deploy a function in your workspace, you are prompted to fill out these settings to configure the function.
 
-First, add a setting in **Settings** tab in the code editor:
+To use settings:
 
-![A screenshot of the functions settings tab](/docs/connections/functions/images/settings-tab-empty.png){:width="500"}
+1. Add a setting in the **Settings** tab in the code editor:
 
-Click **Add Setting** to add your new setting.
+![A screenshot of the functions settings tab](/docs/connections/functions/images/settings-tab-empty.png){:width="500"}
 
-![A screenshot of the "Add Setting" section of the functions settings tab, with apiKey settings included](/docs/connections/functions/images/add-setting-dialog.png)
+2. Click **Add Setting** to add your new setting.
 
-You can configure the details about this setting, which change how it's displayed to anyone using your function:
+3. Configure the details about this setting, which change how it's displayed to anyone using your function:
 
 - **Label** - Name of the setting, which users see when configuring the function.
 - **Name** - Auto-generated name of the setting to use in function's source code.
@@ -21,8 +21,6 @@ You can configure the details about this setting, which change how it's displaye
 
 As you change the values, a preview to the right updates to show how your setting will look and work.
 
-Click **Add Setting** to save the new setting.
+4. Click **Add Setting** to save the new setting.
 
 Once you save a setting, it appears in the **Settings** tab for the function. You can edit or delete settings from this tab.
-
-![A screenshot of the functions settings tab, showing the apiKey setting](/docs/connections/functions/images/settings-tab-non-empty.png){:width="500"}
diff --git a/src/connections/functions/insert-functions.md b/src/connections/functions/insert-functions.md
index 00e32f89b0..12a9147f96 100644
--- a/src/connections/functions/insert-functions.md
+++ b/src/connections/functions/insert-functions.md
@@ -5,15 +5,13 @@ title: Destination Insert Functions
 
 Use Destination Insert Functions to enrich, transform, or filter your data before it reaches downstream destinations.
 
-**Implement advanced data computation**: Write custom computation, operations, and business logic on streaming data that you send to downstream destinations.
+With Destination Insert Functions you can:
+* **Implement advanced data computation**: Write custom computation, operations, and business logic on streaming data that you send to downstream destinations.
+* **Enrich your data**: Use destination insert functions with Segment's Profile API or third party sources to add additional context to your data and create personalized customer experiences.
+* **Support data compliance**: Use destination insert functions to support data masking, encryption, decryption, improved PII data handling, and tokenization.
+* **Customize filtration for your destinations**: Create custom logic with nested if-else statements, regex, custom business rules, and more to filter event data.
 
-**Enrich your data**: Use destination insert functions with Segment's Profile API or third party sources to add additional context to your data and create personalized customer experiences.
-
-**Support data compliance**: Use destination insert functions to support data masking, encryption, decryption, improved PII data handling, and tokenization.
-
-**Customize filtration for your destinations**: Create custom logic with nested if-else statements, regex, custom business rules, and more to filter event data.
-
-> info "Destination Insert Functions are not compatible with IP Allowlisting"
+> info "Destination Insert Functions aren't compatible with IP Allowlisting"
 > For more information, see the [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting) documentation. 
 
 ## Create destination insert functions
@@ -80,7 +78,7 @@ Insert functions can define handlers for each message type in the [Segment spec]
 
 Each of the functions above accepts two arguments:
 
-- **event** - Segment event object, where fields and values depend on the event type. For example, in "Identify" events, Segment formats the object to match the [Identify spec](/docs/connections/spec/identify/).
+- **event** - Segment event object, where fields and values depend on the event type. For example, in Identify events, Segment formats the object to match the [Identify spec](/docs/connections/spec/identify/).
 - **settings** - Set of [settings](#create-settings-and-secrets) for this function.
 
 The example below shows a function that listens for "Track" events, and sends some details about them to an external service.
@@ -104,16 +102,16 @@ async function onTrack(event) {
 }
 ```
 
-To change which event type the handler listens to, you can rename it to the name of the message type. For example, if you rename this function `onIdentify`, it listens for "Identify" events instead.
+To change which event type the handler listens to, you can rename it to the name of the message type. For example, if you rename this function `onIdentify`, it listens for Identify events instead.
 
-To ensure the Destination processes an event payload modified by the function, return the `event` object at the handler's end.
+To ensure the destination processes an event payload modified by the function, return the `event` object at the handler's end.
 
 > info ""
 > Functions' runtime includes a `fetch()` polyfill using a `node-fetch` package. Check out the [node-fetch documentation](https://www.npmjs.com/package/node-fetch){:target="_blank"} for usage examples.
 
 ### Variable scoping 
 
-When declaring settings variables, make sure to declare them in the function handler rather than globally in your function. This prevents you leaking the settings values across other function instances. 
+When declaring settings variables, make sure to declare them in the function handler rather than globally in your function. This prevents you from leaking the settings values across other function instances. 
 
 The handler for insert functions is event-specific, for example, `onTrack()`, `onIdentify()`, and so on.
 
@@ -208,9 +206,9 @@ You may want to consider the [context object's](/docs/connections/spec/common/#c
 
 {% include content/functions/settings.md %}
 
-Next, fill out this setting's value in the **Test** tab, so you can run the function and verify that the correct setting value is passed. (This value is only for testing your function.)
+5. Fill out this setting's value in the **Test** tab, so you can run the function and verify that the correct setting value is passed. (This value is only for testing your function.)
 
-Now that you've configured a setting and entered a test value, you can add code to read its value and run the function, as in the example below:
+6. Add code to read its value and run the function, as in the example below:
 
 ```js
 async function onTrack(request, settings) {