Update tabs config (#395)

* Update tabs config * Add tab end
kyma-project · Jan 15, 2024 · 5fdb527 · 5fdb527
1 parent bd889f7
commit 5fdb527
Show file tree

Hide file tree

Showing 4 changed files with 23 additions and 30 deletions.
diff --git a/docs/user/tutorials/evnt-02-subs-with-multiple-filters.md b/docs/user/tutorials/evnt-02-subs-with-multiple-filters.md
@@ -13,11 +13,9 @@ The [Subscription](../resources/evnt-cr-subscription.md) CustomResourceDefinitio
 
 To subscribe to multiple events, you need a [Subscription](../resources/evnt-cr-subscription.md) custom resource (CR). In the following example, you learn how to subscribe to events of two types: `order.received.v1` and `order.changed.v1`.
 
-<div tabs name="Create a Subscription" group="create-subscription">
-  <details open>
-  <summary label="Kyma Dashboard">
-  Kyma Dashboard
-  </summary>
+<!-- tabs:start -->
+
+#### **Kyma Dashboard**
 
 1. Go to **Namespaces** and select the default namespace.
 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**.
@@ -33,11 +31,7 @@ To subscribe to multiple events, you need a [Subscription](../resources/evnt-cr-
 4. Click **Create**.
 5. Wait a few seconds for the Subscription to have status `READY`.
 
-  </details>
-  <details>
-  <summary label="kubectl">
-  kubectl
-  </summary>
+#### **kubectl**
 
 Run:
 
@@ -65,8 +59,7 @@ kubectl get subscriptions lastorder-sub -o=jsonpath="{.status.ready}"
 
 The operation was successful if the returned status says `true`.
 
-  </details>
-</div>
+<!-- tabs:end -->
 
 ## Trigger the workload with an event
 
@@ -83,7 +76,7 @@ In the following example, you port-forward the [Event Publisher Proxy](../evnt-a
 
 <!-- tabs:start -->
 
-#### CloudEvents Conformance Tool
+#### **CloudEvents Conformance Tool**
 
 ```bash
 cloudevents send http://localhost:3000/publish \
@@ -95,7 +88,7 @@ cloudevents send http://localhost:3000/publish \
    --yaml
 ```
 
-#### curl
+#### **curl**
 
 ```bash
 curl -v -X POST \
@@ -115,7 +108,7 @@ curl -v -X POST \
 
 <!-- tabs:start -->
 
-#### CloudEvents Conformance Tool
+#### **CloudEvents Conformance Tool**
 
 ```bash
 cloudevents send http://localhost:3000/publish \
@@ -127,7 +120,7 @@ cloudevents send http://localhost:3000/publish \
    --yaml
 ```
 
-#### curl
+#### **curl**
 
 ```bash
 curl -v -X POST \

diff --git a/docs/user/tutorials/evnt-03-type-cleanup.md b/docs/user/tutorials/evnt-03-type-cleanup.md
@@ -13,7 +13,7 @@ You learn how Eventing behaves when you create a [Subscription](../resources/evn
 
 <!-- tabs:start -->
 
-#### Kyma Dashboard
+#### **Kyma Dashboard**
 
 ```js
 module.exports = {
@@ -24,7 +24,7 @@ module.exports = {
 }
 ```
 
-#### kubectl
+#### **kubectl**
 
 ```bash
 cat <<EOF | kubectl apply -f -
@@ -60,7 +60,7 @@ Create a [Subscription](../resources/evnt-cr-subscription.md) custom resource (C
 
 <!-- tabs:start -->
 
-#### Kyma Dashboard
+#### **Kyma Dashboard**
 
 1. Go to **Namespaces** and select the default namespace.
 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**.
@@ -74,7 +74,7 @@ Create a [Subscription](../resources/evnt-cr-subscription.md) custom resource (C
 4. Click **Create**.
 5. Wait a few seconds for the Subscription to have status `READY`.
 
-#### kubectl
+#### **kubectl**
 
 Run:
 
@@ -128,7 +128,7 @@ Next, you see that you can still publish events with the original Event name (i.
 
 <!-- tabs:start -->
 
-#### CloudEvents Conformance Tool
+#### **CloudEvents Conformance Tool**
 
 ```bash
 cloudevents send http://localhost:3000/publish \
@@ -140,7 +140,7 @@ cloudevents send http://localhost:3000/publish \
    --yaml
 ```
 
-#### curl
+#### **curl**
 
 ```bash
 curl -v -X POST \

diff --git a/docs/user/tutorials/evnt-04-change-max-in-flight-in-sub.md b/docs/user/tutorials/evnt-04-change-max-in-flight-in-sub.md
@@ -13,7 +13,7 @@ The "in-flight messages" config defines the number of events that Kyma Eventing
 
 <!-- tabs:start -->
 
-#### Kyma Dashboard
+#### **Kyma Dashboard**
 
 ```js
 module.exports = {
@@ -27,7 +27,7 @@ module.exports = {
 }
 ```
 
-#### kubectl
+#### **kubectl**
 
 ```bash
 cat <<EOF | kubectl apply -f -
@@ -67,7 +67,7 @@ Create a [Subscription](../resources/evnt-cr-subscription.md) custom resource (C
 
 <!-- tabs:start -->
 
-#### Kyma Dashboard
+#### **Kyma Dashboard**
 
 1. Go to **Namespaces** and select the default namespace.
 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**.
@@ -82,7 +82,7 @@ Create a [Subscription](../resources/evnt-cr-subscription.md) custom resource (C
 4. Click **Create**.
 5. Wait a few seconds for the Subscription to have status `READY`.
 
-#### kubectl
+#### **kubectl**
 
 Run:
 
@@ -128,7 +128,7 @@ Next, publish 15 events at once and see how Kyma Eventing triggers the workload.
 
 <!-- tabs:start -->
 
-#### CloudEvents Conformance Tool
+#### **CloudEvents Conformance Tool**
 
 ```bash
 for i in {1..15}
@@ -143,7 +143,7 @@ do
 done
 ```
 
-#### curl
+#### **curl**
 
 ```bash
 for i in {1..15}

diff --git a/docs/user/tutorials/evnt-05-send-legacy-events.md b/docs/user/tutorials/evnt-05-send-legacy-events.md
@@ -17,7 +17,7 @@ To subscribe to events, we need a [Subscription](../resources/evnt-cr-subscripti
 
 <!-- tabs:start -->
 
-#### Kyma Dashboard
+#### **Kyma Dashboard**
 
 1. Go to **Namespaces** and select the default namespace.
 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**.
@@ -31,7 +31,7 @@ To subscribe to events, we need a [Subscription](../resources/evnt-cr-subscripti
 4. Click **Create**.
 5. Wait a few seconds for the Subscription to have status `READY`.
 
-#### curl
+#### **curl**
 
 Run: