Remove documentation for now removed group linking

Author: satya164

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

@@ -266,44 +266,6 @@ In the above example, the following path formats are handled:
 - `/user` navigates to the `Profile` screen
 - `/feed/:sort` navigates to the `Chat` screen with the param `sort`
 
-In addition, if you are using [`groups`](group.md) in your navigator, you can specify the `linking` property for the group to apply it to all screens in the group. The path specified in the group will be used as a prefix for all screens in the group. For example:
-
-```js
-const RootStack = createStackNavigator({
-  screens: {
-    Home: {
-      screen: HomeScreen,
-      linking: 'home',
-    },
-  },
-  groups: {
-    // highlight-start
-    Admin: {
-      linking: 'admin',
-      screens: {
-        Dashboard: {
-          screen: DashboardScreen,
-          linking: 'dashboard',
-        },
-        Settings: {
-          screen: SettingsScreen,
-          linking: 'settings',
-        },
-      },
-    },
-    // highlight-end
-  },
-});
-```
-
-This results in:
-
-- `/home` navigates to the `Home` screen
-- `/admin/dashboard` navigates to the `Dashboard` screen
-- `/admin/settings` navigates to the `Settings` screen
-
-Any other options specified for the group such as [`parse` and `stringify`](#passing-params) are shallow merged with the options specified for the screens. If the same option is specified in both the group and the screen, the one specified in the screen will take precedence.
-
 ### How does automatic path generation work?
 
 When using automatic path generation with `enabled: 'auto'`, the following rules are applied:

versioned_docs/version-8.x/upgrading-from-7.x.md

@@ -1141,28 +1141,6 @@ Compared to parse functions, schemas provide a few advantages:
 
 See [Configuring links](configuring-links.md#using-standard-schema) and [TypeScript](typescript.md#parse-function-vs-standard-schema) for more details.
 
-### Groups now support `linking` option in static configuration
-
-The `linking` option can now be specified for groups in static configuration to define nested paths:
-
-```js
-const Stack = createStackNavigator({
-  groups: {
-    Settings: {
-      linking: { path: 'settings' },
-      screens: {
-        UserSettings: 'user',
-        AppSettings: 'app',
-      },
-    },
-  },
-});
-```
-
-This lets you prefix the paths of the screens in the group with a common prefix, e.g. `settings/` for `settings/user` and `settings/app`.
-
-See [Group](group.md) for more details.
-
 ### Deep linking to screens behind conditional screens is now supported
 
 Previously, if a screen was conditionally rendered based on some state (e.g. authentication status), deep linking to that screen wouldn't work since the screen wouldn't exist in the navigator when the app was opened via a deep link.