Fix reno for rabbitmq-user-check

Change-Id: I5eed22ab0230a477d1629545b8ab1aeff33f4a35

diff --git a/manifests/profile/releasenotes/notes/rabbitmq-user-check-95da891a2e197d89.yaml b/releasenotes/notes/rabbitmq-user-check-95da891a2e197d89.yaml
similarity index 72%
rename from manifests/profile/releasenotes/notes/rabbitmq-user-check-95da891a2e197d89.yaml
rename to releasenotes/notes/rabbitmq-user-check-95da891a2e197d89.yaml
index e1caf4c..0857f63 100644 (file)
--- a/manifests/profile/releasenotes/notes/rabbitmq-user-check-95da891a2e197d89.yaml
+++ b/releasenotes/notes/rabbitmq-user-check-95da891a2e197d89.yaml
@@ -1,6 +1,6 @@
 ---
 fixes:
   - The rabbitmq user check is moved to step >= 2 from step >= 1. There
-    is no gaurantee that rabbitmq is running at step 1, especially if
+    is no guarantee that rabbitmq is running at step 1, especially if
     updating a failed stack that never made it past step 1 to begin
     with.