Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/v1.2] Fix typos in shortcodes #1742

Merged
merged 1 commit into from
Sep 25, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sources/configure/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ configMapGenerator:
disableNameSuffixHash: true
```

## Configure {{< param "PRODUCT_NAME" >}}
## Configure {{% param "PRODUCT_NAME" %}}

This section describes how to modify the {{< param "PRODUCT_NAME" >}} configuration, which is stored in a ConfigMap in the Kubernetes cluster.
There are two methods to perform this task.
Expand Down
2 changes: 1 addition & 1 deletion docs/sources/set-up/deploy.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ The Pod’s controller, network configuration, enabled capabilities, and availab

[clustering]: ../../configure/clustering/

## Process different types of telemetry in different {{< param "PRODUCT_NAME" >}} instances
## Process different types of telemetry in different {{% param "PRODUCT_NAME" %}} instances

If the load on {{< param "PRODUCT_NAME" >}} is small, you can process all necessary telemetry signals in the same {{< param "PRODUCT_NAME" >}} process.
For example, a single {{< param "PRODUCT_NAME" >}} deployment can process all of the incoming metrics, logs, traces, and profiles.
Expand Down
Loading