fix(KNO-12271): Add target="_blank" to external links in docs (#1381)

* Update external links to open in new tab

* Update links in tables to add hyperlink styling

* Prettier formatting

* Remove leading space

* Prettier formatting

Author: rachael-t

content/__api-reference/content.mdx

@@ -81,7 +81,7 @@ Each endpoint in the Knock API is rate limited. Knock uses a tier system to dete
 
 Knock's default behavior scopes rate limits based on the authorizing credential used in your requests. When you use a public or private API key to authorize a request, Knock will scope the rate limit for each endpoint by the [environment](/concepts/environments) associated with the key. If you use a signed user token as your authorizing credential, Knock will scope the rate limit by both the key's environment and the signing user. See our documentation on [enhanced security mode](/in-app-ui/security-and-authentication#authentication-with-enhanced-security) for more details on working with signed user tokens.
 
-If you're concerned about exceeding a Knock rate limit, please [contact us](https://knock.app/contact-sales) and we can help figure out a usage rate that's right for your specific needs.
+If you're concerned about exceeding a Knock rate limit, please <a href="https://knock.app/contact-sales" target="_blank" rel="noopener">contact us</a> and we can help figure out a usage rate that's right for your specific needs.
 
 </ContentColumn>
 <ExampleColumn>
@@ -144,7 +144,7 @@ Knock can apply batch deduplication rate limits to all or part of a request. If
 <Section title="Idempotent requests" slug="idempotent-requests" path="/overview/idempotent-requests">
 <ContentColumn>
 
-Knock supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) so that requests can be retried safely without unintended side effects.
+Knock supports <a href="https://en.wikipedia.org/wiki/Idempotence" target="_blank" rel="noopener noreferrer">idempotency</a> so that requests can be retried safely without unintended side effects.
 
 To perform an idempotent request, set an `Idempotency-Key` header on your request. This idempotency key is a unique string of up to 255 characters that you generate for each request. It is used to identify and prevent the duplicate processing of requests. If you retry a request with the same idempotency key within 24 hours from the original request, Knock will return the same response as the original request. Idempotent requests are expected to be identical. To prevent accidental misuse, Knock returns an error when incoming parameters don't match those from the original request.
 
@@ -367,7 +367,7 @@ Resources that return multiple entities support the same cursor-based pagination
 <Section title="Errors" slug="errors" direction="column" path="/overview/errors">
 <ContentColumn>
 
-Knock uses standard [HTTP response codes](https://developer.mozilla.org/en-US/Web/HTTP/Status) to indicate the success or failure of your API requests.
+Knock uses standard <a href="https://developer.mozilla.org/en-US/Web/HTTP/Status" target="_blank" rel="noopener noreferrer">HTTP response codes</a> to indicate the success or failure of your API requests.
 
 - `2xx` success status codes confirm that your request worked as expected.
 

content/__mapi-reference/content.mdx

@@ -72,7 +72,7 @@ Authorization: Bearer knock_st_12345
 <Section title="Errors" slug="errors" path="/overview/errors" direction="column">
 <ContentColumn>
 
-Knock uses standard [HTTP response codes](https://developer.mozilla.org/en-US/Web/HTTP/Status) to indicate the success or failure of your API requests.
+Knock uses standard <a href="https://developer.mozilla.org/en-US/Web/HTTP/Status" target="_blank" rel="noopener noreferrer">HTTP response codes</a> to indicate the success or failure of your API requests.
 
 - `2xx` success status codes confirm that your request worked as expected.
 - `4xx` error status codes indicate an error caused by incorrect or missing request information (e.g. providing an incorrect API key).
@@ -84,7 +84,7 @@ Knock uses standard [HTTP response codes](https://developer.mozilla.org/en-US/We
 <Section title="Postman" slug="postman" path="/overview/postman" direction="column">
 <ContentColumn>
 
-You can use our [Management API Postman collection](https://www.postman.com/knock-labs/workspace/knock-public-workspace/collection/15616728-9ed6000c-13bc-43f5-a2cf-db6daea256bd?action=share&creator=15616728&active-environment=15616728-6df39335-c6f9-4c9d-99d5-73e3c7ffe524) to quickly get started testing our Management API.
+You can use our <a href="https://www.postman.com/knock-labs/workspace/knock-public-workspace/collection/15616728-9ed6000c-13bc-43f5-a2cf-db6daea256bd?action=share&creator=15616728&active-environment=15616728-6df39335-c6f9-4c9d-99d5-73e3c7ffe524" target="_blank" rel="noopener">Management API Postman collection</a> to quickly get started testing our Management API.
 
 </ContentColumn>
 </Section>

content/cli/overview.mdx

@@ -25,7 +25,7 @@ With the CLI, you can:
 
 **Install with Homebrew**
 
-For macOS, you can install the Knock CLI using [Homebrew](https://brew.sh/). Once the CLI is installed you can call it by using the `knock` command in your terminal.
+For macOS, you can install the Knock CLI using <a href="https://brew.sh/" target="_blank" rel="noopener noreferrer">Homebrew</a>. Once the CLI is installed you can call it by using the `knock` command in your terminal.
 
 **Install with npm**
 
@@ -38,7 +38,7 @@ The Knock CLI is built with Node.js and installable as a `npm` package. You must
 - Node.js: 16.14.0 or higher
 - NPM: 7.18.1 or higher
 
-You can find the Knock CLI npm package [here](https://www.npmjs.com/package/@knocklabs/cli).
+You can find the Knock CLI npm package <a href="https://www.npmjs.com/package/@knocklabs/cli" target="_blank" rel="noopener">here</a>.
 
 </ContentColumn>
 <ExampleColumn>

content/concepts/recipients.mdx

@@ -55,7 +55,7 @@ You can use our [Subscriptions](/concepts/subscriptions) feature to create a Kno
 
 ## Recipient timezones
 
-A recipient can have an optional `timezone` property, which should be a [valid tz database time zone string](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), like `America/New_York` or `Europe/London`. By default, if no recipient timezone is set `Etc/UTC` will be used however a [default timezone](/manage-your-account/account-timezone) can be specified at the account level under "Settings" which will override this default for all recipients.
+A recipient can have an optional `timezone` property, which should be a <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones" target="_blank" rel="noopener noreferrer">valid tz database time zone string</a>, like `America/New_York` or `Europe/London`. By default, if no recipient timezone is set `Etc/UTC` will be used however a [default timezone](/manage-your-account/account-timezone) can be specified at the account level under "Settings" which will override this default for all recipients.
 
 ## Frequently asked questions
 

content/concepts/schedules.mdx

@@ -269,7 +269,7 @@ There are 2 ways in which to get data into each of your scheduled workflow runs:
 
 ## Executing schedules in a recipient's timezone
 
-Knock supports a `timezone` property on the recipient that automatically makes a scheduled workflow run timezone aware, meaning you can express recurring schedules like "every monday at 9am in the recipient's timezone." Recipient timezones must be a [valid tz database time zone string](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), like `America/New_York`.
+Knock supports a `timezone` property on the recipient that automatically makes a scheduled workflow run timezone aware, meaning you can express recurring schedules like "every monday at 9am in the recipient's timezone." Recipient timezones must be a <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones" target="_blank" rel="noopener noreferrer">valid tz database time zone string</a>, like `America/New_York`.
 
 [Read more about recipient timezone support](/concepts/recipients#recipient-timezones).
 

content/concepts/tenants.mdx

@@ -208,7 +208,10 @@ that aren't relevant to the user.
   text={
     <>
       Per-tenant branding is only available on our{" "}
-      <a href="https://knock.app/pricing">Enterprise plan</a>.
+      <a href="https://knock.app/pricing" target="_blank" rel="noopener">
+        Enterprise plan
+      </a>
+      .
     </>
   }
 />
@@ -236,7 +239,11 @@ Now that the tenant is set up, when you trigger a workflow with an email step yo
   text={
     <>
       Per-tenant user preferences and tenant preference defaults are only
-      available on our <a href="https://knock.app/pricing">Enterprise plan</a>.
+      available on our{" "}
+      <a href="https://knock.app/pricing" target="_blank" rel="noopener">
+        Enterprise plan
+      </a>
+      .
     </>
   }
 />

content/concepts/users.mdx

@@ -45,13 +45,13 @@ The following attributes are required for each user you identify with Knock.
 
 The following attributes are optional, depending on the channel types you decide to use with Knock.
 
-| Property     | Description                                                                                                                                                                                                                 |
-| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| email        | The primary email address for the user (required for email channels)                                                                                                                                                        |
-| name         | The full name of the user                                                                                                                                                                                                   |
-| avatar       | A URL for the avatar of the user                                                                                                                                                                                            |
-| phone_number | The [E.164](https://www.twilio.com/docs/glossary/what-e164) phone number of the user (required for SMS channels)                                                                                                            |
-| timezone     | A valid [tz database time zone string](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) (optional for [recurring schedules](/concepts/schedules#scheduling-workflows-with-recurring-schedules-for-recipients)) |
+| Property     | Description                                                                                                                                                                                                                                                                                                                                               |
+| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| email        | The primary email address for the user (required for email channels)                                                                                                                                                                                                                                                                                      |
+| name         | The full name of the user                                                                                                                                                                                                                                                                                                                                 |
+| avatar       | A URL for the avatar of the user                                                                                                                                                                                                                                                                                                                          |
+| phone_number | The <a href="https://www.twilio.com/docs/glossary/what-e164" target="\_blank" rel="noopener noreferrer" style={{ color: "var(--tgph-accent-11)", textDecoration: "underline" }}>E.164</a> phone number of the user (required for SMS channels)                                                                                                            |
+| timezone     | A valid <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones" target="\_blank" rel="noopener noreferrer" style={{ color: "var(--tgph-accent-11)", textDecoration: "underline" }}>tz database time zone string</a> (optional for [recurring schedules](/concepts/schedules#scheduling-workflows-with-recurring-schedules-for-recipients)) |
 
 ### Storing user properties
 

content/designing-workflows/batch-function.mdx

@@ -88,7 +88,7 @@ You can also set the length of your batch windows dynamically using a variable.
 
 When specifying a dynamic batch window you must provide one of the following:
 
-- An [ISO-8601 timestamp](https://en.wikipedia.org/wiki/ISO_8601) (e.g. `2022-05-04T20:34:07Z`) which must be a datetime in the future
+- An <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank" rel="noopener noreferrer">ISO-8601 timestamp</a> (e.g. `2022-05-04T20:34:07Z`) which must be a datetime in the future
 - A relative duration (e.g `{ "unit": "seconds", "value": 30 }`)
 - A window rule (e.g `{ "frequency": "daily", "hours": 9, "minutes": 30 }`)
 
@@ -296,7 +296,10 @@ Here's a list of the variables that you can use to work with batch-related state
   text={
     <>
       The render limit setting for batch activities and actors is only available
-      on our <a href="https://knock.app/pricing">Enterprise plan.</a>
+      on our{" "}
+      <a href="https://knock.app/pricing" target="_blank" rel="noopener">
+        Enterprise plan.
+      </a>
     </>
   }
 />

content/designing-workflows/delay-function.mdx

@@ -22,7 +22,7 @@ You can also set the length of your delay dynamically using a variable. You can
 
 When specifying a dynamic delay period you must provide one of the following:
 
-- An [ISO-8601 timestamp](https://en.wikipedia.org/wiki/ISO_8601) (e.g. `2022-05-04T20:34:07Z`) which must be a datetime in the future
+- An <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank" rel="noopener noreferrer">ISO-8601 timestamp</a> (e.g. `2022-05-04T20:34:07Z`) which must be a datetime in the future
 - A duration unit (e.g `{ "unit": "seconds", "value": 30 }`)
 - A window rule (e.g `{ "frequency": "daily", "hours": 9, "minutes": 30 }`)
 

content/designing-workflows/throttle-function.mdx

@@ -33,7 +33,7 @@ You can also set the length of your throttle windows dynamically using a variabl
 
 When specifying a dynamic window you must provide one of the following:
 
-- An **[ISO-8601 timestamp](https://en.wikipedia.org/wiki/ISO_8601)** (e.g. `2022-05-04T20:34:07Z`) which must be a datetime in the future
+- An <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank" rel="noopener noreferrer">ISO-8601 timestamp</a> (e.g. `2022-05-04T20:34:07Z`) which must be a datetime in the future
 - A relative duration unit (e.g `{ "unit": "seconds", "value": 30 }`)
 - A window rule (e.g `{ "frequency": "daily", "hours": 9, "minutes": 30 }`)