Merge pull request dapr#4080 from newbe36524/v1.13

Remove Duplicated keys from head matter

daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md

@@ -4,7 +4,6 @@ title: "How To: Use secret scoping"
 linkTitle: "How To: Use secret scoping"
 weight: 3000
 description: "Use scoping to limit the secrets that can be read by your application from secret stores"
-type: docs
 ---
 
 Once you [configure a secret store for your application]({{< ref setup-secret-store >}}), *any* secret defined within that store is accessible by default from the Dapr application. 
@@ -107,4 +106,4 @@ Scenarios | defaultAccess | allowedSecrets | deniedSecrets | permission
 ## Related links
 
 - List of [secret stores]({{< ref supported-secret-stores.md >}})
-- Overview of [secret stores]({{< ref setup-secret-store.md >}})
+- Overview of [secret stores]({{< ref setup-secret-store.md >}})

daprdocs/content/en/developing-applications/integrations/gRPC-integration.md

@@ -4,7 +4,6 @@ title: "How to: Use the gRPC interface in your Dapr application"
 linkTitle: "How to: gRPC interface"
 weight: 6000
 description: "Use the Dapr gRPC API in your application"
-type: docs
 ---
 
 Dapr implements both an HTTP and a gRPC API for local calls. [gRPC](https://grpc.io/) is useful for low-latency, high performance scenarios and has language integration using the proto clients.

daprdocs/content/en/operations/hosting/kubernetes/kubernetes-job.md

@@ -4,7 +4,6 @@ title: "Running Dapr with a Kubernetes Job"
 linkTitle: "Kubernetes Jobs"
 weight: 70000
 description: "Use Dapr API in a Kubernetes Job context"
-type: docs
 ---
 
 The Dapr sidecar is designed to be a long running process. In the context of a [Kubernetes Job](https://kubernetes.io/docs/concepts/workloads/controllers/job/) this behavior can block your job completion.
@@ -67,4 +66,4 @@ func main() {
 ## Related links
 
 - [Deploy Dapr on Kubernetes]({{< ref kubernetes-deploy.md >}})
-- [Upgrade Dapr on Kubernetes]({{< ref kubernetes-upgrade.md >}})
+- [Upgrade Dapr on Kubernetes]({{< ref kubernetes-upgrade.md >}})

daprdocs/content/en/operations/observability/tracing/otel-collector/open-telemetry-collector-jaeger.md

@@ -4,7 +4,6 @@ title: "Using OpenTelemetry Collector to collect traces to send to Jaeger"
 linkTitle: "Using the OpenTelemetry for Jaeger"
 weight: 1200
 description: "How to push trace events to Jaeger distributed tracing platform, using the OpenTelemetry Collector."
-type: docs
 ---
 
 While Dapr supports writing traces using OpenTelemetry (OTLP) and Zipkin protocols, Zipkin support for Jaeger has been deprecated in favor of OTLP. Although Jaeger supports OTLP directly, the recommended approach for production is to use the OpenTelemetry Collector to collect traces from Dapr and send them to Jaeger, allowing your application to quickly offload data and take advantage of features like retries, batching, and encryption. For more information, read the Open Telemetry Collector [documentation](https://opentelemetry.io/docs/collector/#when-to-use-a-collector).

daprdocs/content/en/operations/observability/tracing/zipkin.md

@@ -4,7 +4,6 @@ title: "How-To: Set up Zipkin for distributed tracing"
 linkTitle: "Zipkin"
 weight: 4000
 description: "Set up Zipkin for distributed tracing"
-type: docs
 ---
 
 ## Configure self hosted mode

daprdocs/content/en/reference/components-reference/supported-middleware/middleware-bearer.md

@@ -3,7 +3,6 @@ type: docs
 title: "Bearer"
 linkTitle: "Bearer"
 description: "Use bearer middleware to secure HTTP endpoints by verifying bearer tokens"
-type: docs
 aliases:
 - /developing-applications/middleware/supported-middleware/middleware-bearer/
 ---