From c41062d888cfe0f74a024d7cb7ff482d8165a714 Mon Sep 17 00:00:00 2001
From: Yiannis Triantafyllopoulos <8741709+yiannistri@users.noreply.github.com>
Date: Wed, 20 Sep 2023 09:39:09 +0100
Subject: [PATCH] fix: Typo

Signed-off-by: Yiannis Triantafyllopoulos <8741709+yiannistri@users.noreply.github.com>
---
 docs/spec/v2beta1/helmreleases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/spec/v2beta1/helmreleases.md b/docs/spec/v2beta1/helmreleases.md
index 6f9561295..556291d2f 100644
--- a/docs/spec/v2beta1/helmreleases.md
+++ b/docs/spec/v2beta1/helmreleases.md
@@ -1027,7 +1027,7 @@ spec:
 ## Role-based access control
 
 By default, a `HelmRelease` runs under the cluster admin account and can create, modify, delete cluster level objects
-(cluster roles, cluster role binding, CRDs, etc) and namespeced objects (deployments, ingresses, etc).
+(cluster roles, cluster role binding, CRDs, etc) and namespaced objects (deployments, ingresses, etc).
 For certain `HelmReleases` a cluster admin may wish to control what types of Kubernetes objects can
 be reconciled and under which namespace.
 To restrict a `HelmRelease`, one can assign a service account under which the reconciliation is performed.