Replace % with <> for admonition shortcode (#1680)

Author: heitortsergent

docs/sources/next/examples/distribute-workloads.md

@@ -14,20 +14,20 @@ For example, most traffic to an e-commerce site might come from users who only s
 The following sections provide examples of how to structure k6 scripts to split logic across VUs.
 To inspect the results for a certain behavior, you can [create a custom metric](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/metrics/create-custom-metrics) or use [Tags](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/tags-and-groups) to filter by scenario, code block, or individual request.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 These techniques can create very complex configurations.
 However, more complexity creates more ambiguity in result interpretation
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Split logic across scenarios
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 In this context, _workload_ refers to the traffic pattern simulated by a scenario.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 One way to distribute traffic is to use scenarios to schedule different workloads for different functions.
 

docs/sources/next/examples/get-started-with-k6/test-for-functional-behavior.md

@@ -142,14 +142,14 @@ k6 run api-test.js
    ✓ response code was 200
    ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 Under larger loads, this check will fail in some iterations.
 **Failed checks do not stop tests.**
 
 Rather, k6 tracks the success rate and presents it in your [end of test](https://grafana.com/docs/k6/<K6_VERSION>/results-output/end-of-test) summary.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Next steps
 

docs/sources/next/examples/get-started-with-k6/test-for-performance.md

@@ -167,13 +167,13 @@ k6 run api-test.js
 The load is small, so the server should perform within thresholds.
 However, this test server may be under load by many k6 learners, so the results are unpredictable.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 At this point, it'd be nice to have a graphical interface to visualize metrics as they occur.
 k6 has many output formats, which can serve as inputs for many visualization tools, both open source and commercial.
 For ideas, read [Ways to visualize k6 results](https://k6.io/blog/ways-to-visualize-k6-results).
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Ramp up until threshold fails
 

docs/sources/next/extensions/build-k6-binary-using-docker.md

@@ -8,11 +8,11 @@ weight: 03
 
 Using the [xk6 Docker image](https://hub.docker.com/r/grafana/xk6/) can simplify the process of creating a custom k6 binary. It avoids having to setup a local Go environment, and install xk6 manually.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 This tutorial is about creating a custom k6 binary (using Docker). If you want to create a Docker image with a custom k6 binary, refer instead to [Using modules with Docker](https://grafana.com/docs/k6/<K6_VERSION>/using-k6/modules/#using-modules-with-docker).
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Building your first extension
 
@@ -126,7 +126,7 @@ Flags:
 
 The use of `--replace` should be considered an advanced feature to be avoided unless required.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 Referring back to our executed command, note that:
 

docs/sources/next/extensions/build-k6-binary-using-go.md

@@ -9,11 +9,11 @@ weight: 02
 To use an extension that you found on the [Extension page](https://grafana.com/docs/k6/<K6_VERSION>/extensions/explore) or the [xk6 GitHub topic](https://github.com/topics/xk6),
 you need to build a binary using Go.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 Not interested in setting up a Go environment? You can [use Docker instead](https://grafana.com/docs/k6/<K6_VERSION>/extensions/build-k6-binary-using-docker/).
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Before you start
 

docs/sources/next/extensions/create/_index.md

@@ -24,12 +24,12 @@ there's some background knowledge you should have:
 - You should be familiar with both Go(lang), JavaScript, and their tooling
 - You should understand how the [_Go-to-JavaScript_](https://grafana.com/docs/k6/<K6_VERSION>/extensions/explanations/go-js-bridge) bridge works within k6
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 If you maintain a public xk6 repository and wish to have your extension listed in our [registry](https://grafana.com/docs/k6/<K6_VERSION>/extensions/explore),
 be sure to review the [requirements](https://grafana.com/docs/k6/<K6_VERSION>/extensions/explanations/extensions-registry#registry-requirements).
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Avoid unneeded work
 

docs/sources/next/extensions/create/javascript-extensions.md

@@ -66,12 +66,12 @@ func (c *Compare) IsGreater(a, b int) bool {
 
 1. Register the module to use these from k6 test scripts.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 k6 extensions must have the `k6/x/` prefix,
 and the short name must be unique among all extensions built in the same k6 binary.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ```go
 import "go.k6.io/k6/js/modules"
@@ -126,12 +126,12 @@ To build a k6 binary with this extension, run this command:
 $ xk6 build --with xk6-compare=.
 ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 When building from source code, `xk6-compare` is the Go module name passed to `go mod init`.
 Usually, this would be a URL similar to `github.com/grafana/xk6-compare`.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Use your extension
 
@@ -180,7 +180,7 @@ interface to serve as a factory of `Compare` instances for each VU.
 
 The significance depends on the size of your module.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 Here's what that would look like:
 
@@ -259,11 +259,11 @@ func (mi *ModuleInstance) Exports() modules.Exports {
 
 {{< /code >}}
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 Notice that we implemented the Module API and now `modules.Register` the _root module_ rather than our _Compare_ object!
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Accessing runtime state
 

docs/sources/next/extensions/create/output-extensions.md

@@ -88,11 +88,11 @@ func init() {
 }
 ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 You must use the registered with the `-o`, or `--out` flag when running k6!
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 The final extension code looks like this:
 
@@ -181,13 +181,13 @@ To build a k6 binary with this extension, run:
 $ xk6 build --with xk6-output-logger=.
 ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 `xk6-output-logger` is the Go module name passed to `go mod init`
 
 Usually, this would be a URL similar to `github.com/grafana/xk6-output-logger`.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Use your extension
 
@@ -215,12 +215,12 @@ export default function () {
 $ ./k6 run test.js --out logger --quiet --no-summary --iterations 2
 ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 The `--out logger` argument tells k6 to use your custom output. The flag
 `--quiet --no-summary` configures k6 to show only custom output.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 Your output should look something like this:
 

docs/sources/next/extensions/explanations/extension-graduation.md

@@ -21,11 +21,11 @@ A _core-bound_ extension passes through the following phases:
 Most extensions in the k6 ecosystem remain _extensions_ requiring [xk6](https://github.com/grafana/xk6) to incorporate the custom functionality.
 These extensions might be provided by Grafana or by the community, and _may_ be included in the [Extensions Registry](https://grafana.com/docs/k6/<K6_VERSION>/extensions/explore).
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 Only Grafana-controlled extensions may progress beyond the _extension_ phase to become _experimental_ or _core modules_.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Experimental Module
 
@@ -44,7 +44,7 @@ The key will be to achieve a balance between usability and stability.
 Not all experimental modules will progress to become a core module!
 The k6 team reserves the right to discontinue and remove any experimental module if is no longer deemed desirable.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ### Core Module
 

docs/sources/next/extensions/explanations/extensions-registry.md

@@ -70,11 +70,11 @@ As an example, suppose an extension that outputs test metrics to the _AwesomeLog
 In this case, say the latest v3 API is not backward-compatible.
 Applying our conventions, we'd recommend naming this repository as `xk6-output-awesomelog-v2`.
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 Our goal is to quickly understand the intent of the extension.
 
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Extension Tiers