Markdown linting

Author: rcastley

content/en/imt/dashboards/signalflow.md

@@ -36,11 +36,13 @@ Also, you can copy the SignalFlow and use it when interacting with the API or wi
 
 {{< tabs >}}
 {{% tab name="SignalFlow" %}}
+
 ```python
 A = data('demo.trans.latency', filter=filter('demo_datacenter', 'Paris')).percentile(pct=95).publish(label='A', enable=False)
 B = data('demo.trans.latency', filter=filter('demo_datacenter', 'Paris')).percentile(pct=95).timeshift('1w').publish(label='B', enable=False)
 C = (A-B).publish(label='C')
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 

content/en/tko/session-5/docs/edit-hpa.md

@@ -12,11 +12,6 @@ Increase the `maxReplicas` to 8
 ``` bash
 kubectl edit hpa php-apache -n apache
 ```
-<<<<<<< HEAD
-=======
-
-Save the changes youhave made. (Hint: Use `Esc` followed by `:wq!` to save your changes).
->>>>>>> main
 
 Save the changes youhave made. (Hint: Use `Esc` followed by `:wq!` to save your changes).
 

content/en/tko/session-6/docs/lambda.md

@@ -295,8 +295,8 @@ Look at all these differences!
 
 Notice how we are now importing some OpenTelemetry libraries directly into our function to handle some of the manual instrumenation tasks we require.
 
-We are using https://www.npmjs.com/package/@opentelemetry/api to manipulate the tracing logic in our functions.
-We are using https://www.npmjs.com/package/@opentelemetry/core to access the **Propagator** objects that we will use to manually propagate our context with.
+We are using <https://www.npmjs.com/package/@opentelemetry/api> to manipulate the tracing logic in our functions.
+We are using <https://www.npmjs.com/package/@opentelemetry/core> to access the **Propagator** objects that we will use to manually propagate our context with.
 
 The bellow code executes the following steps inside the Producer function:
 
@@ -425,8 +425,8 @@ Note how the *Trace ID* is something that makes up the trace *context* that we p
 
 You can read up on the two common propagation standards:
 
-1. W3C: https://www.w3.org/TR/trace-context/#traceparent-header
-2. B3: https://github.com/openzipkin/b3-propagation#overall-process
+1. W3C: <https://www.w3.org/TR/trace-context/#traceparent-header>
+2. B3: <https://github.com/openzipkin/b3-propagation#overall-process>
 
 Which one are we using? *It should be self-explanatory from the Propagator we are creating in the Functions*
 

content/ja/imt/dashboards/adding-charts.md

@@ -36,7 +36,6 @@ isCJKLanguage: true
 
 ![Three Dashboard](../../images/M-MoreCharts-6.png)
 
-
 ## 3. 貼り付けたチャートを編集する
 
 ダッシュボードの **Latency History** チャートの3つの点 **`...`** をクリックし、**Open** をクリックします（または、チャートの名前（ここでは **Latency History**）をクリックすることもできます）。

content/ja/imt/dashboards/signalflow.md

@@ -37,11 +37,13 @@ SignalFlow の詳細については、 [Analyze incoming data using SignalFlow](
 
 {{< tabs >}}
 {{% tab name="SignalFlow" %}}
+
 ```python
 A = data('demo.trans.latency', filter=filter('demo_datacenter', 'Paris')).percentile(pct=95).publish(label='A', enable=False)
 B = data('demo.trans.latency', filter=filter('demo_datacenter', 'Paris')).percentile(pct=95).timeshift('1w').publish(label='B', enable=False)
 C = (A-B).publish(label='C')
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 

content/ja/imt/gdi/_index.md

@@ -35,17 +35,21 @@ Kubernetes が起動したら、Splunk の UI から Access Token[^1] を取得
 
 {{< tabs >}}
 {{% tab name="Export ACCESS TOKEN" %}}
+
 ```bash
 export ACCESS_TOKEN="<replace_with_O11y-Workshop-ACCESS_TOKEN>"
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
 {{< tabs >}}
 {{% tab name="Export REALM" %}}
+
 ```bash
 export REALM="<replace_with_REALM>"
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -75,6 +79,7 @@ Update Complete. ⎈Happy Helming!⎈
 
 {{< tabs >}}
 {{% tab name="Helm Install" %}}
+
 ```bash
 helm install splunk-otel-collector \
 --set="splunkObservability.realm=$REALM" \
@@ -87,6 +92,7 @@ helm install splunk-otel-collector \
 splunk-otel-collector-chart/splunk-otel-collector \
 -f ~/workshop/k3s/otel-collector.yaml
 ```
+
 {{% /tab %}}
 {{% tab name="Helm Install Output" %}}
 Using ACCESS_TOKEN={REDACTED}
@@ -99,6 +105,7 @@ REVISION: 1
 TEST SUITE: None
 {{% /tab %}}
 {{% tab name="Install Network Explorer" %}}
+
 ```bash
 helm install splunk-otel-collector \
 --set="splunkObservability.realm=$REALM" \
@@ -117,6 +124,7 @@ helm install splunk-otel-collector \
 splunk-otel-collector-chart/splunk-otel-collector \
 -f ~/workshop/k3s/otel-collector.yaml
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -126,14 +134,20 @@ splunk-otel-collector-chart/splunk-otel-collector \
 
 {{< tabs >}}
 {{% tab name="Kubectl Get Pods" %}}
+
 ```bash
 kubectl get pods
 ```
+
 {{% /tab %}}
 {{% tab name="Kubectl Get Pods Output" %}}
+
+``` text
 NAME                                                          READY   STATUS    RESTARTS   AGE
 splunk-otel-collector-agent-2sk6k                             0/1     Running   0          10s
 splunk-otel-collector-k8s-cluster-receiver-6956d4446f-gwnd7   0/1     Running   0          10s
+```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -143,11 +157,15 @@ OpenTelemetry Collector podのログを確認して、エラーがないこと
 
 {{< tabs >}}
 {{% tab name="Kubectl Logs" %}}
+
 ```bash
 kubectl logs -l app=splunk-otel-collector -f --container otel-collector
 ```
+
 {{% /tab %}}
 {{% tab name="Kubectl Logs Output" %}}
+
+``` text
 2021-03-21T16:11:10.900Z        INFO    service/service.go:364  Starting receivers...
 2021-03-21T16:11:10.900Z        INFO    builder/receivers_builder.go:70 Receiver is starting... {"component_kind": "receiver", "component_type": "prometheus", "component_name": "prometheus"}
 2021-03-21T16:11:11.009Z        INFO    builder/receivers_builder.go:75 Receiver started.       {"component_kind": "receiver", "component_type": "prometheus", "component_name": "prometheus"}
@@ -158,6 +176,8 @@ kubectl logs -l app=splunk-otel-collector -f --container otel-collector
 2021-03-21T16:11:11.009Z        INFO    service/service.go:267  Everything is ready. Begin running and processing data.
 2021-03-21T16:11:11.009Z        INFO    [email protected]/receiver.go:59       Starting shared informers and wait for initial cache sync.      {"component_kind": "receiver", "component_type": "k8s_cluster", "component_name": "k8s_cluster"}
 2021-03-21T16:11:11.281Z        INFO    [email protected]/receiver.go:75       Completed syncing shared informer caches.       {"component_kind": "receiver", "component_type": "k8s_cluster", "component_name": "k8s_cluster"}
+```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -167,6 +187,7 @@ OpenTelemetry Collectorのインストールに失敗した場合は、次のよ
 ``` sh
 helm delete splunk-otel-collector
 ```
+
 {{% /notice %}}
 
 ---
@@ -183,9 +204,11 @@ Splunk の UI で左下の **>>** を開いて **Infrastructure** をクリッ
 
 {{< tabs >}}
 {{% tab name="Echo Cluster Name" %}}
+
 ```bash
 echo $(hostname)-k3s-cluster
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -198,7 +221,7 @@ echo $(hostname)-k3s-cluster
 ![Filtered K8S Cluster](../images/filtered-k3s-cluster.png)
 
 ノードの状態を確認するには、クラスターの淡いブルーの背景にカーソルを置き、左上に表示される青い虫眼鏡をクリックしてください 。
-![Magnifying Glass](../images/blue-cross.png) 
+![Magnifying Glass](../images/blue-cross.png)
 
 これで、ノードレベルまでドリルダウンできます。 次に、サイドバーボタンをクリックしてサイドバーを開き、Metricsサイドバーを開きます。
 

content/ja/imt/gdi/nginx.md

@@ -24,9 +24,11 @@ Multipass または AWS/EC2 のシェルセッションで、`nginx` ディレ
 
 {{< tabs >}}
 {{% tab name="Change Directory" %}}
+
 ```bash
 cd ~/workshop/k3s/nginx
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -38,22 +40,30 @@ NGINX の ConfigMap[^1] を `nginx.conf` ファイルを使って作成します
 
 {{< tabs >}}
 {{% tab name="Kubectl Configmap Create" %}}
+
 ```bash
 kubectl create configmap nginxconfig --from-file=nginx.conf
 ```
+
 {{% /tab %}}
 {{% tab name="Kubectl Create Configmap Output" %}}
+
+``` text
 configmap/nginxconfig created
+```
+
 {{% /tab %}}
 {{< /tabs >}}
 
 続いて、デプロイメントを作成します。
 
 {{< tabs >}}
 {{% tab name="Kubectl Create Deployment" %}}
+
 ```bash
 kubectl create -f nginx-deployment.yaml
 ```
+
 {{% /tab %}}
 {{% tab name="Kubectl Create Deployment Output" %}}
 deployment.apps/nginx created
@@ -65,15 +75,19 @@ service/nginx created
 
 {{< tabs >}}
 {{% tab name="Kubectl Create Deployment" %}}
+
 ```bash
 kubectl create -f locust-deployment.yaml
 ```
+
 {{% /tab %}}
 {{% tab name="Kubectl Create Deployment Output" %}}
+
 ```bash
 deployment.apps/nginx-loadgenerator created
 service/nginx-loadgenerator created
 ```
+
 {{% /tab %}}
 {{< /tabs >}}
 
@@ -95,11 +109,15 @@ Pod が実行状態に移行するまでには 20 秒程度しかかかりませ
 
 {{< tabs >}}
 {{% tab name="Kubectl Get Pods" %}}
+
 ```bash
 kubectl get pods
 ```
+
 {{% /tab %}}
 {{% tab name="Kubectl Get Pods Output" %}}
+
+``` text
 NAME                                                          READY   STATUS    RESTARTS   AGE
 splunk-otel-collector-k8s-cluster-receiver-77784c659c-ttmpk   1/1     Running   0          9m19s
 splunk-otel-collector-agent-249rd                             1/1     Running   0          9m19s
@@ -110,6 +128,8 @@ nginx-7b95fb6b6b-hlx27                                        1/1     Running
 nginx-7b95fb6b6b-zwns9                                        1/1     Running   0          5m57s
 svclb-nginx-loadgenerator-nscx4                               1/1     Running   0          2m20s
 nginx-loadgenerator-755c8f7ff6-x957q                          1/1     Running   0          2m20s
+```
+
 {{% /tab %}}
 {{< /tabs >}}
 

content/ja/imt/monitoring-as-code/_index.md

@@ -26,15 +26,16 @@ AWS/EC2 インスタンスにログインして、`o11y-cloud-jumpstart` ディ
 
 {{< tabs >}}
 {{% tab name="Change directory" %}}
+
 ```bash
 cd observability-content-contrib/integration-examples/terraform-jumpstart
 ```
+
 {{</tab >}}
 {{< /tabs >}}
 
 必要な環境変数は、[Helmによるインストール](../gdi/#2-helmによるインストール) ですでに設定されているはずです。そうでない場合は、以下の Terraform のステップで使用するために、以下の環境変数を作成してください。
 
-
 {{< tabs >}}
 {{% tab name="Export ACCESS TOKEN" %}}
 
@@ -63,11 +64,15 @@ Splunk Terraform Provider の新バージョンがリリースされるたびに
 
 {{< tabs >}}
 {{% tab name="Initialise Terraform" %}}
+
 ```bash
 terraform init -upgrade
 ```
+
 {{</tab >}}
 {{% tab name="Initialise Output" %}}
+
+``` text
     Upgrading modules...
     - aws in modules/aws
     - azure in modules/azure
@@ -106,6 +111,8 @@ terraform init -upgrade
     If you ever set or change modules or backend configuration for Terraform,
     rerun this command to reinitialize your working directory. If you forget, other
     commands will detect it and remind you to do so if necessary.
+```
+
 {{</tab >}}
 {{< /tabs >}}
 
@@ -150,22 +157,30 @@ Plan: 146 to add, 0 to change, 0 to destroy.
 
 {{< tabs >}}
 {{% tab name="Apply Plan" %}}
+
 ```bash
 terraform apply -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM" -var="o11y_prefix=[$(hostname)]"
 ```
+
 {{</tab >}}
 {{% tab name="Apply Plan Output" %}}
+
+``` text
 Apply complete! Resources: 146 added, 0 changed, 0 destroyed.
+```
+
 {{</tab >}}
 {{< /tabs >}}
 
 適用が完了したら、 **Alerts → Detectors** でディテクターが作成されたことを確認してください。ディテクターのプレフィックスには、インスタンスのホスト名が入ります。プレフィックスの値を確認するには以下を実行してください。
 
 {{< tabs >}}
 {{% tab name="Echo Hostname" %}}
+
 ```bash
 echo $(hostname)
 ```
+
 {{</tab >}}
 {{< /tabs >}}
 
@@ -183,12 +198,18 @@ echo $(hostname)
 
 {{< tabs >}}
 {{% tab name="Destroy" %}}
+
 ```bash
 terraform destroy -var="access_token=$ACCESS_TOKEN" -var="realm=$REALM"
 ```
+
 {{</tab >}}
 {{% tab name="Destroy Output" %}}
+
+``` text
 Destroy complete! Resources: 146 destroyed.
+```
+
 {{</tab >}}
 {{< /tabs >}}