Remove note about prefixes since it's optional now

Author: satya164

versioned_docs/version-8.x/configuring-links.md

@@ -121,7 +121,11 @@ const linking = {
 
 If not specified, it defaults to `['*']`, which will match any host starting with `http`, `https`, and custom schemes such as `myapp://`. You only need to specify `prefixes` if you're using **Expo Go** or want to restrict the URLs your app handles.
 
-Note that the `prefixes` option has no effect on Web. The host & domain names will be automatically determined from the Website URL in the browser.
+:::info
+
+The `prefixes` option has no effect on Web. The host & domain names will be automatically determined from the Website URL in the browser.
+
+:::
 
 ### Multiple subdomains​
 

versioned_docs/version-8.x/static-configuration.md

@@ -186,20 +186,6 @@ const RootStack = createNativeStackNavigator({
 
 The `linking` object supports the same configuration options described in [Configuring links](configuring-links.md) such as `parse`, `stringify` and `exact`.
 
-To make deep links work on native apps, you also need to [configure your app](deep-linking.md) and pass `prefixes` to the navigation component returned by [`createStaticNavigation`](static-configuration.md#createstaticnavigation):
-
-```js
-const Navigation = createStaticNavigation(RootStack);
-
-const linking = {
-  prefixes: ['https://example.com', 'example://'],
-};
-
-function App() {
-  return <Navigation linking={linking} />;
-}
-```
-
 #### `if`
 
 Callback to determine whether the screen should be rendered or not. It doesn't receive any arguments. This can be useful for conditional rendering of screens, e.g. - if you want to render a different screen for logged in users.