Remove experimental note for web examples

Author: satya164

versioned_docs/version-5.x/link.md

@@ -4,8 +4,6 @@ title: Link
 sidebar_label: Link
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `Link` component lets us navigate to a screen using a path instead of a screen name based on the [`linking` options](navigation-container.md#linking). It preserves the default behavior of anchor tags in the browser such as `Right click -> Open link in new tab"`, `Ctrl+Click`/`⌘+Click` etc.
 
 It uses a `Text` component under the hood.

versioned_docs/version-5.x/server-container.md

@@ -4,8 +4,6 @@ title: ServerContainer
 sidebar_label: ServerContainer
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `ServerContainer` component provides utilities to render your app on server with the correct [navigation state](navigation-state.md).
 
 Example:

versioned_docs/version-5.x/server-rendering.md

@@ -4,8 +4,6 @@ title: Server rendering
 sidebar_label: Server rendering
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 This guide will cover how to server render your React Native app using React Native for Web and React Navigation. We'll cover the following cases:
 
 1. Rendering the correct layout depending on the request URL

versioned_docs/version-5.x/use-link-builder.md

@@ -4,8 +4,6 @@ title: useLinkBuilder
 sidebar_label: useLinkBuilder
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `useLinkBuilder` hook let's us build a path to use for links for a screen in the current navigator's state. It returns a function that takes `name` and `params` for the screen to focus and returns path based on the [`linking` options](navigation-container.md#linking).
 
 ```js

versioned_docs/version-5.x/use-link-props.md

@@ -4,8 +4,6 @@ title: useLinkProps
 sidebar_label: useLinkProps
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `useLinkProps` hook let's build our custom link components which let us navigate to a screen using a path instead of a screen name based on the [`linking` options](navigation-container.md#linking). It takes a path and returns an object with some props that you can pass to a component.
 
 Example:

versioned_docs/version-5.x/use-link-to.md

@@ -4,8 +4,6 @@ title: useLinkTo
 sidebar_label: useLinkTo
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `useLinkTo` hook let's us navigate to a screen using a path instead of a screen name based on the [`linking` options](navigation-container.md#linking). It returns a function that receives the path to navigate to.
 
 ```js

versioned_docs/version-6.x/link.md

@@ -4,8 +4,6 @@ title: Link
 sidebar_label: Link
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `Link` component lets us navigate to a screen using a path instead of a screen name based on the [`linking` options](navigation-container.md#linking). It preserves the default behavior of anchor tags in the browser such as `Right click -> Open link in new tab"`, `Ctrl+Click`/`⌘+Click` etc.
 
 It uses a `Text` component under the hood.

versioned_docs/version-6.x/server-container.md

@@ -4,8 +4,6 @@ title: ServerContainer
 sidebar_label: ServerContainer
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `ServerContainer` component provides utilities to render your app on server with the correct [navigation state](navigation-state.md).
 
 Example:

versioned_docs/version-6.x/server-rendering.md

@@ -4,8 +4,6 @@ title: Server rendering
 sidebar_label: Server rendering
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 This guide will cover how to server render your React Native app using React Native for Web and React Navigation. We'll cover the following cases:
 
 1. Rendering the correct layout depending on the request URL

versioned_docs/version-6.x/use-link-builder.md

@@ -4,7 +4,6 @@ title: useLinkBuilder
 sidebar_label: useLinkBuilder
 ---
 
-> Note: This API is experimental and might change in a minor version.
 
 The `useLinkBuilder` hook let's us build a path to use for links for a screen in the current navigator's state. It returns a function that takes `name` and `params` for the screen to focus and returns path based on the [`linking` options](navigation-container.md#linking).
 
@@ -32,4 +31,4 @@ This hook is intended to be used in navigators to show links to various pages in
 There are couple of important things to note:
 
 - The destination screen must be present in the current navigator. It cannot be in a parent navigator or a navigator nested in a child.
-- It's intended to be only used in custom navigators to keep them reusable in multiple apps. For your regular app code, use paths directly instead of building paths for screens.
+- It's intended to be only used in custom navigators to keep them reusable in multiple apps. For your regular app code, use paths directly instead of building paths for screens, or use [`Link`](link.md) and [`useLinkProps`](use-link-props.md) which transparently handle paths.

versioned_docs/version-6.x/use-link-props.md

@@ -4,8 +4,6 @@ title: useLinkProps
 sidebar_label: useLinkProps
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `useLinkProps` hook let's build our custom link components which let us navigate to a screen using a path instead of a screen name based on the [`linking` options](navigation-container.md#linking). It takes a path and returns an object with some props that you can pass to a component.
 
 Example:

versioned_docs/version-6.x/use-link-to.md

@@ -4,8 +4,6 @@ title: useLinkTo
 sidebar_label: useLinkTo
 ---
 
-> Note: This API is experimental and might change in a minor version.
-
 The `useLinkTo` hook let's us navigate to a screen using a path instead of a screen name based on the [`linking` options](navigation-container.md#linking). It returns a function that receives the path to navigate to.
 
 ```js