fix: Update docs link to portal compatibility for v8 theme migration

microsoft · Dec 9, 2024 · 966678c · 966678c
1 parent 592b73f
commit 966678c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/apps/public-docsite-v9/src/Concepts/Migration/FromV8/Components/Theme.stories.mdx b/apps/public-docsite-v9/src/Concepts/Migration/FromV8/Components/Theme.stories.mdx
@@ -21,7 +21,7 @@ Beyond consistency with the latest Fluent Design system, this change provides si
 
 #### Portals
 
-To be use v9 components inside v8 components like `Panel` & `Callout`, please enable [portal compatibility](?path=/docs/concepts-migration-from-v8-troubleshooting--page).
+To be use v9 components inside v8 components like `Panel` & `Callout`, please enable [portal compatibility](?path=/docs/concepts-migration-from-v8-troubleshooting--docs#portal-compatibility).
 
 ### Theme (v8) => Theme (v9)
 

diff --git a/apps/public-docsite-v9/src/Concepts/Migration/FromV8/Troubleshooting.stories.mdx b/apps/public-docsite-v9/src/Concepts/Migration/FromV8/Troubleshooting.stories.mdx
@@ -43,7 +43,7 @@ function App() {
 }
 ```
 
-## "I tried uing a layered v8 component like Callout in a layered v9 component like Dialog and my Callout appears beneath my Dialog. What's going on?"
+## <a id="portal-compatibility"></a> "I tried using a layered v8 component like Callout in a layered v9 component like Dialog and my Callout appears beneath my Dialog. What's going on?"
 
 Both v9 and v8 layers set the same `z-index` value by default, which means the document order will resolve their z-positioning.
 This can lead to inconsistent behavior because z-positioning depends on the order in which elements appear in the DOM.