docs: rename navgating to navigating (#24216)

(cherry picked from commit 7d6417a)

src/material-experimental/mdc-menu/menu.spec.ts

@@ -2058,7 +2058,7 @@ describe('MDC-based MatMenu', () => {
         .toBe(true);
     }));
 
-    it('should restore focus to a nested trigger when navgating via the keyboard', fakeAsync(() => {
+    it('should restore focus to a nested trigger when navigating via the keyboard', fakeAsync(() => {
       compileTestComponent();
       instance.rootTriggerEl.nativeElement.click();
       fixture.detectChanges();

src/material/menu/menu.spec.ts

@@ -2053,7 +2053,7 @@ describe('MatMenu', () => {
         .toBe(true);
     }));
 
-    it('should restore focus to a nested trigger when navgating via the keyboard', fakeAsync(() => {
+    it('should restore focus to a nested trigger when navigating via the keyboard', fakeAsync(() => {
       compileTestComponent();
       instance.rootTriggerEl.nativeElement.click();
       fixture.detectChanges();

src/material/tabs/tabs.md

@@ -96,7 +96,7 @@ between content within a single page.
 elements as the "tabs". You should use this component when you want your cross-page navigation to
 look like a tabbed interface. As a rule of thumb, you should consider `MatTabNavBar` if changing
 tabs would change the browser URL. For all navigation, including with `MatTabNavBar`, always move
-browser focus to an element at the beginning of the content to which the user is navgating.
+browser focus to an element at the beginning of the content to which the user is navigating.
 Furthermore, consider placing your `<router-outlet>` inside of a
 [landmark region](https://www.w3.org/TR/wai-aria-1.1/#dfn-landmark) appropriate to the page.