Changed "navigate" to "go"

doc/development/documentation/styleguide/index.md

@@ -1137,10 +1137,10 @@ When documenting navigation through the user interface:
 
 - Use the exact wording as shown in the UI, including any capital letters as-is.
 - Use bold text for navigation items and the char "greater than" (`>`) as a
-  separator. For example: `Navigate to your project's **Settings > CI/CD**`.
+  separator. For example: `From your project, go to **Settings > CI/CD**`.
 - If there are any expandable menus, make sure to mention that the user needs to
   expand the tab to find the settings you're referring to. For example:
-  `Navigate to your project's **Settings > CI/CD** and expand **General pipelines**`.
+  `From your group, go to **Settings > CI/CD** and expand **General pipelines**`.
 
 ### Navigational elements
 
@@ -1436,10 +1436,10 @@ readability of the text.
 For example, the following adds little to the accompanying text:
 
 ```markdown
-1. Go to **{home}** **Project overview > Details**
+1. Go to **{home}** **Project overview > Details**.
 ```
 
-1. Go to **{home}** **Project overview > Details**
+1. Go to **{home}** **Project overview > Details**.
 
 However, the following might help the reader connect the text to the user
 interface: