chore: revert invalid changes

Author: sean-perkins

docs/angular/navigation.md

@@ -118,6 +118,10 @@ export class LoginComponent {
 
 Both options provide the same navigation mechanism, just fitting different use cases.
 
+:::note
+A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported
+:::
+
 ### Navigating using LocationStrategy.historyGo
 
 Angular Router has a [LocationStrategy.historyGo](https://angular.io/api/common/LocationStrategy#historyGo) method that allows developers to move forward or backward through the application history. Let's take a look at an example.

versioned_docs/version-v5/angular/navigation.md

@@ -109,6 +109,10 @@ export class LoginComponent {
 
 Both options provide the same navigation mechanism, just fitting different use cases.
 
+:::note
+A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported
+:::
+
 ## Lazy loading routes
 
 Now the current way our routes are setup makes it so they are included in the same chunk as the root app.module, which is not ideal. Instead, the router has a setup that allows the components to be isolated to their own chunks.