From bdebc128f7c38557f2977b356a125af9f19befb9 Mon Sep 17 00:00:00 2001
From: Josh Keife <jkeife@gmail.com>
Date: Thu, 27 Jun 2024 00:47:08 -0600
Subject: [PATCH] Update vmalert.md (#6539)

Fix typo

### Describe Your Changes

Fix typo in the vmalert docs. In the docs it states rules at `VMAgent`'s
namespace when it should be `VMAlert`'s namespace.

### Checklist

The following checks are **mandatory**:

- [x] My change adheres [VictoriaMetrics contributing
guidelines](https://docs.victoriametrics.com/contributing/).

(cherry picked from commit 8d01dd0514ce0a0fb58baa79434a00526b03bafc)
---
 docs/operator/resources/vmalert.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/operator/resources/vmalert.md b/docs/operator/resources/vmalert.md
index 0e43ff4942..2aa7dde9dc 100644
--- a/docs/operator/resources/vmalert.md
+++ b/docs/operator/resources/vmalert.md
@@ -63,7 +63,7 @@ Following rules are applied:
 
 - If `ruleNamespaceSelector` and `ruleSelector` both undefined, then by default select nothing. With option set - `spec.selectAllByDefault: true`, select all vmrules.
 - If `ruleNamespaceSelector` defined, `ruleSelector` undefined, then all vmrules are matching at namespaces for given `ruleNamespaceSelector`.
-- If `ruleNamespaceSelector` undefined, `ruleSelector` defined, then all vmrules at `VMAgent`'s namespaces are matching for given `ruleSelector`.
+- If `ruleNamespaceSelector` undefined, `ruleSelector` defined, then all vmrules at `VMAlert`'s namespaces are matching for given `ruleSelector`.
 - If `ruleNamespaceSelector` and `ruleSelector` both defined, then only vmrules at namespaces matched `ruleNamespaceSelector` for given `ruleSelector` are matching.
 
 Here's a more visual and more detailed view: