Backport of docs: Search Refresh Fixes into release/1.13.x (#14659)

This pull request was automerged via backport-assistant
hashicorp · Sep 16, 2022 · 2866390 · 2866390
1 parent 4087241
commit 2866390
Show file tree

Hide file tree

Showing 135 changed files with 171 additions and 171 deletions.
diff --git a/website/content/docs/agent/config-entries.mdx b/website/content/docs/agent/config-entries.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: How to Use Configuration Entries
 description: >-
-Configuration entries define the behavior of Consul service mesh components. Learn how to use the `consul config` command to create, manage, and delete configuration entries.
+  Configuration entries define the behavior of Consul service mesh components. Learn how to use the `consul config` command to create, manage, and delete configuration entries.
 ---
 
 # How to Use Configuration Entries

diff --git a/website/content/docs/agent/config/cli-flags.mdx b/website/content/docs/agent/config/cli-flags.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Agents: CLI Reference
+page_title: Agents - CLI Reference
 description: >-
-Add flags to the `consul agent` command to configure agent properties and actions from the CLI. Learn about configurable options and how to format them with examples.
+  Add flags to the `consul agent` command to configure agent properties and actions from the CLI. Learn about configurable options and how to format them with examples.
 ---
 
 # Agents Command-line Reference ((#commandline_options))

diff --git a/website/content/docs/agent/config/config-files.mdx b/website/content/docs/agent/config/config-files.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Agents: Configuration File Reference
+page_title: Agents - Configuration File Reference
 description: >-
-Use agent configuration files to assign attributes to agents and configure multiple agents at once. Learn about agent configuration file parameters and formatting with this reference page and sample code.
+  Use agent configuration files to assign attributes to agents and configure multiple agents at once. Learn about agent configuration file parameters and formatting with this reference page and sample code.
 ---
 
 # Agents Configuration File Reference ((#configuration_files))

diff --git a/website/content/docs/agent/config/index.mdx b/website/content/docs/agent/config/index.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Agents: Configuration Explained
+page_title: Agents - Configuration Explained
 description: >-
-Agent configuration is the process of defining server and client agent properties with CLI flags and configuration files. Learn what properties can be configured on reload and how Consul sets precedence for configuration settings.
+  Agent configuration is the process of defining server and client agent properties with CLI flags and configuration files. Learn what properties can be configured on reload and how Consul sets precedence for configuration settings.
 ---
 
 # Agent Configuration

diff --git a/website/content/docs/agent/index.mdx b/website/content/docs/agent/index.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Agents Overview
 description: >-
-Agents maintain register services, respond to queries, maintain datacenter membership information, and make most of Consul’s functions possible. Learn how to start, stop, and configure agents, as well as their requirements and lifecycle.
+  Agents maintain register services, respond to queries, maintain datacenter membership information, and make most of Consul’s functions possible. Learn how to start, stop, and configure agents, as well as their requirements and lifecycle.
 ---
 
 # Agents Overview

diff --git a/website/content/docs/agent/rpc.mdx b/website/content/docs/agent/rpc.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Legacy RPC Protocol
 description: >-
-Consul agents originally could be controlled through the RPC protocol. This feature was deprecated in version 0.8 in favor of the HTTP API. Learn about agent RPC interactions and how they worked.
+  Consul agents originally could be controlled through the RPC protocol. This feature was deprecated in version 0.8 in favor of the HTTP API. Learn about agent RPC interactions and how they worked.
 ---
 
 # RPC Protocol

diff --git a/website/content/docs/agent/sentinel.mdx b/website/content/docs/agent/sentinel.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Sentinel ACL Policies (Enterprise)
 description: >-
-Sentinel allows you to include conditional logic in access control policies. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities for controlling key-value (KV) write access.
+  Sentinel allows you to include conditional logic in access control policies. Learn how Consul can use Sentinel policies to extend the ACL system's capabilities for controlling key-value (KV) write access.
 ---
 
 # Sentinel for KV ACL Policy Enforcement

diff --git a/website/content/docs/agent/telemetry.mdx b/website/content/docs/agent/telemetry.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Agents: Enable Metrics
+page_title: Agents - Enable Telemetry Metrics
 description: >-
-Configure agent telemetry to collect operations metrics you can use to debug and observe Consul behavior and performance. Learn about configuration options, the metrics you can collect, and why they're important.
+  Configure agent telemetry to collect operations metrics you can use to debug and observe Consul behavior and performance. Learn about configuration options, the metrics you can collect, and why they're important.
 ---
 
 # Agent Telemetry

diff --git a/website/content/docs/architecture/anti-entropy.mdx b/website/content/docs/architecture/anti-entropy.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Anti-Entropy Enforcement
 description: >-
-Anti-entropy keeps distributed systems consistent. Learn how Consul uses an anti-entropy mechanism to periodically sync agent states with the service catalog to prevent the catalog from becoming stale.
+  Anti-entropy keeps distributed systems consistent. Learn how Consul uses an anti-entropy mechanism to periodically sync agent states with the service catalog to prevent the catalog from becoming stale.
 ---
 
 # Anti-Entropy Enforcement

diff --git a/website/content/docs/architecture/consensus.mdx b/website/content/docs/architecture/consensus.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Consensus Protocol | Raft
 description: >-
-Consul ensures a consistent state using the Raft protocol. A quorum, or a majority of server agents with one leader, agree to state changes before committing to the state log. Learn how Raft works in Consul to ensure state consistency and how that state can be read with different consistency modes to balance read latency and consistency.
+  Consul ensures a consistent state using the Raft protocol. A quorum, or a majority of server agents with one leader, agree to state changes before committing to the state log. Learn how Raft works in Consul to ensure state consistency and how that state can be read with different consistency modes to balance read latency and consistency.
 ---
 
 # Consensus Protocol

diff --git a/website/content/docs/architecture/coordinates.mdx b/website/content/docs/architecture/coordinates.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Network Coordinates
 description: >-
-Network coordinates are node locations in network tomography used to estimate round trip time (RTT). Learn how network coordinates manifest in Consul, how it calculates RTT, and how to work with coordinates to sort catalog information by nearness to a given node.
+  Network coordinates are node locations in network tomography used to estimate round trip time (RTT). Learn how network coordinates manifest in Consul, how it calculates RTT, and how to work with coordinates to sort catalog information by nearness to a given node.
 ---
 
 # Network Coordinates

diff --git a/website/content/docs/architecture/gossip.mdx b/website/content/docs/architecture/gossip.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Gossip Protocol | Serf
 description: >-
-Consul agents manage membership in datacenters and WAN federations using the Serf protocol. Learn about the differences between LAN and WAN gossip pools and how `serfHealth` affects health checks.
+  Consul agents manage membership in datacenters and WAN federations using the Serf protocol. Learn about the differences between LAN and WAN gossip pools and how `serfHealth` affects health checks.
 ---
 
 # Gossip Protocol

diff --git a/website/content/docs/architecture/improving-consul-resilience.mdx b/website/content/docs/architecture/improving-consul-resilience.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Fault Tolerance in Consul
 description: >-
-Fault tolerance is a system's ability to operate without interruption despite component failure. Learn how a set of Consul servers provide fault tolerance through use of a quorum, and how to further improve control plane resilience through use of infrastructure zones and Enterprise redundancy zones.
+  Fault tolerance is a system's ability to operate without interruption despite component failure. Learn how a set of Consul servers provide fault tolerance through use of a quorum, and how to further improve control plane resilience through use of infrastructure zones and Enterprise redundancy zones.
 ---
 
 # Fault Tolerance

diff --git a/website/content/docs/architecture/index.mdx b/website/content/docs/architecture/index.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Consul Architecture
 description: >-
-Consul datacenters consist of clusters of server agents (control plane) and client agents deployed alongside service instances (dataplane). Learn how these components and their different communication methods make Consul possible.
+  Consul datacenters consist of clusters of server agents (control plane) and client agents deployed alongside service instances (dataplane). Learn how these components and their different communication methods make Consul possible.
 ---
 
 # Consul Internals Overview

diff --git a/website/content/docs/architecture/jepsen.mdx b/website/content/docs/architecture/jepsen.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Consistency Verification | Jepsen Testing Results
 description: >-
-Jepsen is a tool to measure the reliability and consistency of distributed systems across network partitions. Learn about the Jepsen testing performed on Consul to ensure it gracefully recovers from partitions and maintains consistent state.
+  Jepsen is a tool to measure the reliability and consistency of distributed systems across network partitions. Learn about the Jepsen testing performed on Consul to ensure it gracefully recovers from partitions and maintains consistent state.
 ---
 
 # Jepsen Testing Results

diff --git a/website/content/docs/concepts/service-discovery.mdx b/website/content/docs/concepts/service-discovery.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Service Discovery Explained
 description: >-
-Service discovery dynamically tracks and monitors service instances on your network and makes them discoverable through DNS queries. Learn about the benefits of service discovery and how it works.
+  Service discovery dynamically tracks and monitors service instances on your network and makes them discoverable through DNS queries. Learn about the benefits of service discovery and how it works.
 ---
 
 # What is service discovery?

diff --git a/website/content/docs/concepts/service-mesh.mdx b/website/content/docs/concepts/service-mesh.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Service Mesh Explained
 description: >-
-Service mesh is a dedicated network layer for secure, resilient, observable microservice communication. Learn about using Consul's service mesh to solve service networking challenges in application architectures and manage complexity in multi-cloud, hybrid cloud, and multi-platform environments.
+  Service mesh is a dedicated network layer for secure, resilient, observable microservice communication. Learn about using Consul's service mesh to solve service networking challenges in application architectures and manage complexity in multi-cloud, hybrid cloud, and multi-platform environments.
 ---
 
 # What is a service mesh?

diff --git a/website/content/docs/connect/ca/aws.mdx b/website/content/docs/connect/ca/aws.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Service Mesh Certificate Authority: AWS Certificate Manager
+page_title: Service Mesh Certificate Authority - AWS Certificate Manager
 description: >-
-You can use the AWS Certificate Manager Private Certificate Authority as the Consul service mesh's certificate authority  to secure your service mesh. Learn how to configure the AWS ACM Private CA, its limitations in Consul, and cost planning considerations.
+  You can use the AWS Certificate Manager Private Certificate Authority as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the AWS ACM Private CA, its limitations in Consul, and cost planning considerations.
 ---
 
 # AWS Certificate Manager as a Service Mesh Certificate Authority

diff --git a/website/content/docs/connect/ca/consul.mdx b/website/content/docs/connect/ca/consul.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Certificate Authority: Built-in Service Mesh CA
+page_title: Certificate Authority - Built-in Service Mesh CA
 description: >-
-Consul has a built-in service mesh certificate authority that can be used to secure your service mesh without needing a separate CA system. Learn how to configure the built-in service mesh CA as a root CA or an intermediate CA connected to an existing PKI system.
+  Consul has a built-in service mesh certificate authority that can be used to secure your service mesh without needing a separate CA system. Learn how to configure the built-in service mesh CA as a root CA or an intermediate CA connected to an existing PKI system.
 ---
 
 # Built-In Certificate Authority for Service Mesh

diff --git a/website/content/docs/connect/ca/index.mdx b/website/content/docs/connect/ca/index.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Service Mesh Certificate Authority: Overview
+page_title: Service Mesh Certificate Authority - Overview
 description: >-
-Consul uses a certificate authority (CA) to generate, use, manage, sign, and store certificates for your service mesh. Learn about certificate management, including configuration, root cert rotation, cross-signing, and regenerating the CA.
+  Consul uses a certificate authority (CA) to generate, use, manage, sign, and store certificates for your service mesh. Learn about certificate management, including configuration, root cert rotation, cross-signing, and regenerating the CA.
 ---
 
 # Service Mesh Certificate Authority Overview

diff --git a/website/content/docs/connect/ca/vault.mdx b/website/content/docs/connect/ca/vault.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Service Mesh Certificate Authority: Vault
+page_title: Service Mesh Certificate Authority - Vault
 description: >-
-You can use a Vault PKI secrets engine as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the Vault CA as a root CA or an intermediate CA connected to an existing PKI system, and how to manage PKI paths with either Vault or Consul.
+  You can use a Vault PKI secrets engine as the Consul service mesh's certificate authority to secure your service mesh. Learn how to configure the Vault CA as a root CA or an intermediate CA connected to an existing PKI system, and how to manage PKI paths with either Vault or Consul.
 ---
 
 # Vault as a Service Mesh Certificate Authority

diff --git a/website/content/docs/connect/cluster-peering/create-manage-peering.mdx b/website/content/docs/connect/cluster-peering/create-manage-peering.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Cluster Peering: Create and Manage Connections
+page_title: Cluster Peering - Create and Manage Connections
 description: >-
-Generate a peering token to establish communication, export services, and authorize requests for cluster peering connections. Learn how to create, list, read, check, and delete peering connections.
+  Generate a peering token to establish communication, export services, and authorize requests for cluster peering connections. Learn how to create, list, read, check, and delete peering connections.
 ---
 
 # Create and Manage Cluster Peering Connections

diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Service Mesh: What is Cluster Peering?
+page_title: Service Mesh - What is Cluster Peering?
 description: >-
-Cluster peering establishes communication between independent clusters in Consul, allowing services to interact across datacenters. Learn about the cluster peering process, differences with WAN federation for multi-datacenter deployments, and technical constraints.  
+  Cluster peering establishes communication between independent clusters in Consul, allowing services to interact across datacenters. Learn about the cluster peering process, differences with WAN federation for multi-datacenter deployments, and technical constraints.  
 ---
 
 # What is Cluster Peering?

diff --git a/website/content/docs/connect/cluster-peering/k8s.mdx b/website/content/docs/connect/cluster-peering/k8s.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Cluster Peering on Kubernetes
 description: >-
-If you use Consul on Kubernetes, learn how to enable cluster peering, create peering CRDs, and then manage peering connections in consul-k8s.
+  If you use Consul on Kubernetes, learn how to enable cluster peering, create peering CRDs, and then manage peering connections in consul-k8s.
 ---
 
 # Cluster Peering on Kubernetes

diff --git a/website/content/docs/connect/config-entries/exported-services.mdx b/website/content/docs/connect/config-entries/exported-services.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Exported Services: Configuration Entry Reference
+page_title: Exported Services - Configuration Entry Reference
 description: >-
-An exported services configuration entry defines the availability of a cluster's services to cluster peers and local admin partitions. Learn about `"exported-services"` config entry parameters and exporting services to other datacenters.
+  An exported services configuration entry defines the availability of a cluster's services to cluster peers and local admin partitions. Learn about `""exported-services""` config entry parameters and exporting services to other datacenters.
 ---
 
 # Exported Services Configuration Entry

diff --git a/website/content/docs/connect/config-entries/index.mdx b/website/content/docs/connect/config-entries/index.mdx
@@ -2,7 +2,7 @@
 layout: docs
 page_title: Configuration Entry Overview
 description: >-
-Configuration entries define service mesh behaviors in order to secure and manage traffic. Learn about Consul’s different config entry kinds and get links to configuration reference pages.
+  Configuration entries define service mesh behaviors in order to secure and manage traffic. Learn about Consul’s different config entry kinds and get links to configuration reference pages.
 ---
 
 # Configuration Entry Overview

diff --git a/website/content/docs/connect/config-entries/ingress-gateway.mdx b/website/content/docs/connect/config-entries/ingress-gateway.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Ingress Gateway: Configuration Entry Reference
+page_title: Ingress Gateway - Configuration Entry Reference
 description: >-
-The ingress gateway configuration entry kind defines behavior to secure incoming communication between the service mesh and external sources. Use the reference guide to learn about `"ingress-gateway"` config entry parameters and exposing TCP and HTTP listeners.
+  The ingress gateway configuration entry kind defines behavior to secure incoming communication between the service mesh and external sources. Use the reference guide to learn about `""ingress-gateway""` config entry parameters and exposing TCP and HTTP listeners.
 ---
 
 # Ingress Gateway Configuration Entry

diff --git a/website/content/docs/connect/config-entries/mesh.mdx b/website/content/docs/connect/config-entries/mesh.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Mesh: Configuration Entry Reference
+page_title: Mesh - Configuration Entry Reference
 description: >-
-The mesh configuration entry kind defines global default settings like TLS version requirements for proxies inside the service mesh. Use the reference guide to learn about `""mesh""` config entry parameters and how to control communication with services outside of the mesh.
+  The mesh configuration entry kind defines global default settings like TLS version requirements for proxies inside the service mesh. Use the reference guide to learn about `""mesh""` config entry parameters and how to control communication with services outside of the mesh.
 ---
 
 # Mesh Configuration Entry

diff --git a/website/content/docs/connect/config-entries/proxy-defaults.mdx b/website/content/docs/connect/config-entries/proxy-defaults.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Proxy Defaults: Configuration Entry Reference
+page_title: Proxy Defaults - Configuration Entry Reference
 description: >-
-The proxy defaults configuration entry kind defines default behaviors for sidecar proxies in the service mesh. Use the reference guide to learn about `""proxy-defaults""` config entry parameters and how to expose HTTP paths through Envoy.
+  The proxy defaults configuration entry kind defines default behaviors for sidecar proxies in the service mesh. Use the reference guide to learn about `""proxy-defaults""` config entry parameters and how to expose HTTP paths through Envoy.
 ---
 
 # Proxy Defaults Configuration Entry

diff --git a/website/content/docs/connect/config-entries/service-defaults.mdx b/website/content/docs/connect/config-entries/service-defaults.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Service Defaults: Configuration Entry Reference
+page_title: Service Defaults - Configuration Entry Reference
 description: >-
-The service defaults configuration entry kind defines sets of default configurations that apply to all services in the mesh. Use the examples learn how to define a default protocol, default upstream configuration, and default terminating gateway.
+  The service defaults configuration entry kind defines sets of default configurations that apply to all services in the mesh. Use the examples learn how to define a default protocol, default upstream configuration, and default terminating gateway.
 ---
 
 # Service Defaults Configuration Entry

diff --git a/website/content/docs/connect/config-entries/service-intentions.mdx b/website/content/docs/connect/config-entries/service-intentions.mdx
@@ -1,8 +1,8 @@
 ---
 layout: docs
-page_title: Service Intentions: Configuration Entry Reference
+page_title: Service Intentions - Configuration Entry Reference
 description: >-
-The service intentions configuration entry kind defines the communication permissions between service types. Use the reference guide to learn about `""service-intentions""` config entry parameters and how to authorize L4 and L7 communication int he service mesh with intentions.
+  The service intentions configuration entry kind defines the communication permissions between service types. Use the reference guide to learn about `""service-intentions""` config entry parameters and how to authorize L4 and L7 communication int he service mesh with intentions.
 ---
 
 # Service Intentions Configuration Entry ((#service-intentions))