diff --git a/docs/sources/configure/kubernetes.md b/docs/sources/configure/kubernetes.md
index ca9df50f9c..3b61eaed69 100644
--- a/docs/sources/configure/kubernetes.md
+++ b/docs/sources/configure/kubernetes.md
@@ -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.
diff --git a/docs/sources/set-up/deploy.md b/docs/sources/set-up/deploy.md
index 1aa55b2cd6..55afd7dddf 100644
--- a/docs/sources/set-up/deploy.md
+++ b/docs/sources/set-up/deploy.md
@@ -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.