Fix Blockquote issues

Author: ppcano

src/data/markdown/docs/02 javascript api/01 Init context/open.md

@@ -11,7 +11,7 @@ Opens a file, reading all its contents into memory for use in the script. Favour
 
 #### Function only available in "init context"
 
-This is a function that can only be called from the init context (aka `init code`), code in the global context that is, outside of the main export default function { ... }.
+This is a function that can only be called from the init context (aka **init code**), code in the global context that is, outside of the main export default function { ... }.
 
 By restricting it to the init context, we can easily determine what local files are needed to run the test and thus what we need to bundle up when distributing the test to multiple nodes in a clustered/distributed test.
 

src/data/markdown/docs/02 javascript api/07 k6-metrics/73 Trend.md

@@ -32,14 +32,11 @@ The unit of these variables and functions are all in milliseconds.
 - `p(50) < 200` // half of requests must finish within 200ms.
 - `max < 3000` // the slowest request must finish within 3s.
 
-<Blockquote mod="warning">
 
-#### ⚠️ Don't use `min` and `max` in thresholds
+> #### ⚠️ Don't use `min` and `max` in thresholds
+> We don't recommend using `min` and `max` for specifying thresholds because these
+> values represent outliers. Use percentiles instead.
 
-We don't recommend using `min` and `max` for specifying thresholds because these
-values represent outliers. Use percentiles instead.
-
-</Blockquote>
 
 ### Examples
 

src/data/markdown/docs/03 cloud/03 Integrations/04 Token.md

@@ -7,30 +7,19 @@ Before you can interact with the k6 Cloud service, whether it's for streaming re
 
 Below are some examples on how to utilize the token to authenticate.
 
-<Blockquote mod="warning">
 
-#### Google/GitHub Single Sign-On Users
+> #### Google/GitHub Single Sign-On Users
+> For Single Sign-On (SSO) users, `k6 login cloud` requires a k6 cloud account email and password. You will need to create a password by using [Forgot Password](), or you'll instead need to <a href="https://app.k6.io/account/token"> get your API authentication token from the app</a> and supply that explicitly: `k6 login cloud --token YOUR_API_AUTH_TOKEN`.
+> <a href="#authenticating-with-api-token">See below</a> for more information.
 
-For Single Sign-On (SSO) users, `k6 login cloud` requires a k6 cloud account email and password. You will need to create a password by using [Forgot Password](), or you'll instead need to <a href="https://app.k6.io/account/token"> get your API authentication token from the app</a> and supply that explicitly: `k6 login cloud --token YOUR_API_AUTH_TOKEN`.
-<a href="#authenticating-with-api-token">See below</a> for more information.
+> #### Docker Users
+> If you're running k6 in a Docker container you'll need to make sure that the k6 config file where the k6 cloud API authentication information (an API authentication token) will be stored to is persisted via a Docker volume to the host machine using the `-c/--config PATH/TO/CONFIG_FILE` CLI flag, e.g. `docker run -i -v /path/on-host:/path/in-container/ loadimpact/k6 login cloud -c /path/in-container/config.json`.
 
-</Blockquote>
 
-<Blockquote mod="warning">
 
-#### Docker Users
+> #### Integrating with CI
+> If you are integrating k6 into your CI pipeline, we recommend using one of the token methods to authenticate and not exposing your username/password within your CI configuration files or as variables.
 
-If you're running k6 in a Docker container you'll need to make sure that the k6 config file where the k6 cloud API authentication information (an API authentication token) will be stored to is persisted via a Docker volume to the host machine using the `-c/--config PATH/TO/CONFIG_FILE` CLI flag, e.g. `docker run -i -v /path/on-host:/path/in-container/ loadimpact/k6 login cloud -c /path/in-container/config.json`.
-
-</Blockquote>
-
-<Blockquote mod="warning">
-
-#### Integrating with CI
-
-If you are integrating k6 into your CI pipeline, we recommend using one of the token methods to authenticate and not exposing your username/password within your CI configuration files or as variables.
-
-</Blockquote>
 
 ## Authenticate with email/password
 

src/data/markdown/docs/03 cloud/03 Integrations/05 Cloud APM.md

@@ -41,11 +41,8 @@ The `metrics` parameter allows you to specify built-in and custom metrics to be
 - iterations
 - vus
 
-<Blockquote mod="warning">
 
-A typical use case is to only export custom metrics defined in the script. To do that you should specify the names of your custom metrics in the `metrics` parameter, and set `include_default_metrics` to false.
-
-</Blockquote>
+> A typical use case is to only export custom metrics defined in the script. To do that you should specify the names of your custom metrics in the `metrics` parameter, and set `include_default_metrics` to false.
 
 If you want to export metrics with more granularity, consider using a lower number for the `resample_rate`, like 1.
 

src/data/markdown/docs/03 cloud/04 Project and Team Management/01 Organizations.md

@@ -3,13 +3,10 @@ title: 'Organizations'
 excerpt: 'Explanation of organizations and the hierarchy in the k6 web app'
 ---
 
-<Blockquote mod="warning">
 
-<b>Running tests in another Organization</b>
-
-If you have been invited to another organization as a Team Member, you must specify a projectID in `ext.loadimpact.projectID` in order to use that organization's subscription to run your test.
-
-</Blockquote>
+> **Runing tests in another Organization**
+> 
+> If you have been invited to another organization as a Team Member, you must specify a projectID in `ext.loadimpact.projectID` in order to use that organization's subscription to run your test.
 
 ## Background
 

src/data/markdown/docs/03 cloud/04 Project and Team Management/03 Team Members.md

@@ -3,13 +3,10 @@ title: 'Team Members'
 excerpt: 'Guide on inviting Team Members to your k6 account for collaboration'
 ---
 
-<Blockquote mod="warning">
 
-<b>Team Members must specify a `projectID`</b>
-
-Invited Team members must specify a `projectID` in `options.ext.loadimpact.projectID` of the options object of their test in order to use the subscription of the organization they have been invited to.
-
-</Blockquote>
+> <b>Team Members must specify a `projectID`</b>
+> 
+> Invited Team members must specify a `projectID` in `options.ext.loadimpact.projectID` of the options object of their test in order to use the subscription of the organization they have been invited to.
 
 ## Background