From 309654cece2292fb09959055e8602b9b6dc68077 Mon Sep 17 00:00:00 2001 From: Chromo-residuum-opec Date: Sun, 23 Oct 2022 00:10:34 +0000 Subject: [PATCH] docs: fix 'bellow' typos (#11038) Signed-off-by: backfire-monism-net Signed-off-by: backfire-monism-net --- docs/operator-manual/metrics.md | 4 ++-- docs/proposals/proxy-extensions.md | 2 +- docs/user-guide/diffing.md | 4 ++-- docs/user-guide/sync-options.md | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/operator-manual/metrics.md b/docs/operator-manual/metrics.md index a4a7f5eb918c6..6f24ffba3d3a9 100644 --- a/docs/operator-manual/metrics.md +++ b/docs/operator-manual/metrics.md @@ -9,7 +9,7 @@ Metrics about applications. Scraped at the `argocd-metrics:8082/metrics` endpoin |--------|:----:|-------------| | `argocd_app_info` | gauge | Information about Applications. It contains labels such as `sync_status` and `health_status` that reflect the application state in ArgoCD. | | `argocd_app_k8s_request_total` | counter | Number of kubernetes requests executed during application reconciliation | -| `argocd_app_labels` | gauge | Argo Application labels converted to Prometheus labels. Disabled by default. See section bellow about how to enable it. | +| `argocd_app_labels` | gauge | Argo Application labels converted to Prometheus labels. Disabled by default. See section below about how to enable it. | | `argocd_app_reconcile` | histogram | Application reconciliation performance. | | `argocd_app_sync_total` | counter | Counter for application sync history | | `argocd_cluster_api_resource_objects` | gauge | Number of k8s resource objects in the cache. | @@ -41,7 +41,7 @@ Some examples are: As the Application labels are specific to each company, this feature is disabled by default. To enable it, add the `--metrics-application-labels` flag to the ArgoCD application controller. -The example bellow will expose the ArgoCD Application labels `team-name` and `business-unit` to Prometheus: +The example below will expose the ArgoCD Application labels `team-name` and `business-unit` to Prometheus: containers: - command: diff --git a/docs/proposals/proxy-extensions.md b/docs/proposals/proxy-extensions.md index cde27bc29a877..0ba5b48885b44 100644 --- a/docs/proposals/proxy-extensions.md +++ b/docs/proposals/proxy-extensions.md @@ -166,7 +166,7 @@ the following API base path: `/api/v1/extensions/` -With the configuration bellow, the expected behavior is explained in the +With the configuration below, the expected behavior is explained in the following examples: ```yaml diff --git a/docs/user-guide/diffing.md b/docs/user-guide/diffing.md index 458459a769a87..ed8bf4d054909 100644 --- a/docs/user-guide/diffing.md +++ b/docs/user-guide/diffing.md @@ -81,7 +81,7 @@ data: - '.webhooks[]?.clientConfig.caBundle' ``` -Resource customization can also be configured to ignore all differences made by a managedField.manager at the system level. The example bellow shows how to configure Argo CD to ignore changes made by `kube-controller-manager` in `Deployment` resources. +Resource customization can also be configured to ignore all differences made by a managedField.manager at the system level. The example below shows how to configure Argo CD to ignore changes made by `kube-controller-manager` in `Deployment` resources. ```yaml data: @@ -90,7 +90,7 @@ data: - kube-controller-manager ``` -It is possible to configure ignoreDifferences to be applied to all resources in every Application managed by an Argo CD instance. In order to do so, resource customizations can be configured like in the example bellow: +It is possible to configure ignoreDifferences to be applied to all resources in every Application managed by an Argo CD instance. In order to do so, resource customizations can be configured like in the example below: ```yaml data: diff --git a/docs/user-guide/sync-options.md b/docs/user-guide/sync-options.md index 41512bf464898..387ce85341ab3 100644 --- a/docs/user-guide/sync-options.md +++ b/docs/user-guide/sync-options.md @@ -236,7 +236,7 @@ spec: ## Respect ignore difference configs -This sync option is used to enable Argo CD to consider the configurations made in the `spec.ignoreDifferences` attribute also during the sync stage. By default, Argo CD uses the `ignoreDifferences` config just for computing the diff between the live and desired state which defines if the application is synced or not. However during the sync stage, the desired state is applied as-is. The patch is calculated using a 3-way-merge between the live state the desired state and the `last-applied-configuration` annotation. This sometimes leads to an undesired results. This behavior can be changed by setting the `RespectIgnoreDifferences=true` sync option like in the example bellow: +This sync option is used to enable Argo CD to consider the configurations made in the `spec.ignoreDifferences` attribute also during the sync stage. By default, Argo CD uses the `ignoreDifferences` config just for computing the diff between the live and desired state which defines if the application is synced or not. However during the sync stage, the desired state is applied as-is. The patch is calculated using a 3-way-merge between the live state the desired state and the `last-applied-configuration` annotation. This sometimes leads to an undesired results. This behavior can be changed by setting the `RespectIgnoreDifferences=true` sync option like in the example below: ```yaml apiVersion: argoproj.io/v1alpha1