(no commit message)

diff --git a/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn b/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn
index df94c1919068b5fc790e6245b7cd919f6f51c1e3..88ded7b10cfe8e282b6a7fb4581ead051628bc54 100644 (file)
--- a/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn
+++ b/posts/2023-04-20-fluxcd2-kustomization-delegation-caveats.mdwn
@@ -1,6 +1,6 @@
 Hi,
 
-when you use fluxcd2 to allow teams/apps to be seperated into namesapces and wanna use Principle of least Privilege/limit to the target namespace, be carefull with the following:
+when you use fluxcd2 to allow teams/apps to be seperated into namesapces and wanna use Principle of least Privilege/limit to the target namespace, be careful with the following:
 
 * Errors around secrets are masked as "error: data values must be of type string" as per (this discussion)[https://github.com/fluxcd/flux2/discussions/2355]
     - disable/remove them for testing, otherwhise you can't debug, this is a gross UX issue.