fixed typo in valuen and trft

Signed-off-by: danish siddiqui <[email protected]>

content/docs/1.12/deployment.md

@@ -100,7 +100,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
 
 
 ## Collectors

content/docs/1.13/deployment.md

@@ -105,7 +105,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 
 ## Collectors

content/docs/1.14/deployment.md

@@ -105,7 +105,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
 
 ## Collectors
 

content/docs/1.15/deployment.md

@@ -107,7 +107,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
 
 ## Collectors
 

content/docs/1.16/deployment.md

@@ -107,7 +107,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
 
 ## Collectors
 

content/docs/1.16/operator.md

@@ -976,7 +976,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.17/deployment.md

@@ -107,7 +107,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`.
 
 ## Collectors
 

content/docs/1.17/operator.md

@@ -701,16 +701,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1142,7 +1142,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.18/deployment.md

@@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 ## Collectors
 

content/docs/1.18/operator.md

@@ -717,16 +717,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1158,7 +1158,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.19/deployment.md

@@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 ## Collectors
 

content/docs/1.19/operator.md

@@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.20/deployment.md

@@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 ## Collectors
 

content/docs/1.20/operator.md

@@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.21/deployment.md

@@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 ## Collectors
 

content/docs/1.21/operator.md

@@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.22/deployment.md

@@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 ## Collectors
 

content/docs/1.22/operator.md

@@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```
 

content/docs/1.23/deployment.md

@@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution
 
 ### Agent level tags
 
-Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
+Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set.
 
 ## Collectors
 

content/docs/1.23/operator.md

@@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta
   imagePullPolicy: IfNotPresent
   ports:
     - containerPort: 5775
-      name: zk-compact-trft
+      name: zk-compact-thrift
       protocol: UDP
     - containerPort: 5778
       name: config-rest
       protocol: TCP
     - containerPort: 6831
-      name: jg-compact-trft
+      name: jg-compact-thrift
       protocol: UDP
     - containerPort: 6832
-      name: jg-binary-trft
+      name: jg-binary-thrift
       protocol: UDP
     - containerPort: 14271
       name: admin-http
@@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela
         - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250
         ports:
         - containerPort: 6831
-          name: jg-compact-trft
+          name: jg-compact-thrift
           protocol: UDP
 ```