feat(combo): update combo overview topics

docs/angular/src/content/en/components/angular-reactive-form-validation.mdx

@@ -182,7 +182,7 @@ export class MyComponent implements OnInit {
 
 Related topics:
 
-- [Combo](/combo)
+- [Combo](/inputs/combo/overview)
 - [Select](/select)
 - [Input Group](/input-group)
 - [Date Picker](/date-picker)

docs/angular/src/content/en/components/combo-features.mdx

@@ -229,7 +229,7 @@ Additional components and/or directives with relative APIs that were used:
 
 <hr/>
 
-- [ComboBox Component](/combo)
+- [ComboBox Component](/inputs/combo/overview)
 - [ComboBox Remote Binding](/combo-remote)
 - [ComboBox Templates](/combo-templates)
 - [Template Driven Forms Integration](/input-group)

docs/angular/src/content/en/components/combo-remote.mdx

@@ -227,7 +227,7 @@ A service needs to be included as a provider.
 
 ### Handling Selection
 
-When using a combobox bound to remote data loaded in chunks and dealing with a more complex data type (e.g. objects), it is necessary to define a `valueKey`. As stated in the [combobox topic](/combo#data-value-and-display-properties), when no `valueKey` is specified, the combobox will try to handle selection by `equality (===)`. Since the objects that will be marked as selected will not be the same as the object that are continuously loaded, the selection will fail.
+When using a combobox bound to remote data loaded in chunks and dealing with a more complex data type (e.g. objects), it is necessary to define a `valueKey`. As stated in the [combobox topic](/inputs/combo/overview#data-binding), when no `valueKey` is specified, the combobox will try to handle selection by `equality (===)`. Since the objects that will be marked as selected will not be the same as the object that are continuously loaded, the selection will fail.
 
 <DocsAside type="info">
 When binding a combobox to remote data, make sure to specify a `valueKey`, representing a property that is unique to each item.
@@ -243,7 +243,7 @@ When the combobox is bound to remote data, setting value/selected items through
 
 <hr/>
 
-- [ComboBox Component](/combo)
+- [ComboBox Component](/inputs/combo/overview)
 - [ComboBox Features](/combo-features)
 - [ComboBox Templates](/combo-templates)
 - [Template Driven Forms Integration](/input-group)

docs/angular/src/content/en/components/combo-templates.mdx

@@ -177,7 +177,7 @@ When used with templates, the `igxComboClearIcon` and the `igxComboToggleIcon` s
 
 <hr/>
 
-- [ComboBox Component](/combo)
+- [ComboBox Component](/inputs/combo/overview)
 - [ComboBox Features](/combo-features)
 - [ComboBox Remote Binding](/combo-remote)
 - [Template Driven Forms Integration](/input-group)

docs/angular/src/content/en/components/expansion-panel.mdx

@@ -199,7 +199,7 @@ We can do that by passing content in an `igx-expansion-panel-icon` tag:
 
 Our Angular Expansion Panel will now render "Show More" when the panel is collapsed and "Show Less" once it's fully expanded.
 
-The `IgxExpansionPanel` control allows all sorts of content to be added inside of the `igx-expansion-panel-body`. It can render [`IgxGrid`](/grid/grid)s, [`IgxCombo`](/combo), charts and even other expansion panels!
+The `IgxExpansionPanel` control allows all sorts of content to be added inside of the `igx-expansion-panel-body`. It can render [`IgxGrid`](/grid/grid)s, [`IgxCombo`](/inputs/combo/overview), charts and even other expansion panels!
 
 For the sake of simplicity let's add some basic markup to the body of our expansion panel.
 

docs/angular/src/content/en/components/general/cli/component-templates.mdx

@@ -59,7 +59,7 @@ These templates generate components into an existing Angular workspace only. The
 | snackbar                        | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c snackbar newSnackbar</code><br />Ignite UI CLI:<br /><code>ig add snackbar newSnackbar</code><details>Basic IgxSnackbar sample.</details>                                                                                                                                            | [IgxSnackbar](../../snackbar.mdx) showing a brief message with an optional action.                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | toast                           | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c toast newToast</code><br />Ignite UI CLI:<br /><code>ig add toast newToast</code><details>Basic IgxToast sample.</details>                                                                                                                                                           | [IgxToast](../../toast.mdx) showing a non-interactive notification.                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
 | <b>Data Entry & Display</b>     |                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| combo                           | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c combo newCombo</code><br />Ignite UI CLI:<br /><code>ig add combo newCombo</code><details>Basic IgxCombo with templating.</details>                                                                                                                                                        | [IgxCombo](../../combo.mdx) with custom [templating](../../combo-templates.mdx).                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| combo                           | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c combo newCombo</code><br />Ignite UI CLI:<br /><code>ig add combo newCombo</code><details>Basic IgxCombo with templating.</details>                                                                                                                                                        | [IgxCombo](../../inputs/combo/overview.mdx) with custom [templating](../../combo-templates.mdx).                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | simple-combo                    | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c simple-combo newSimpleCombo</code><br />Ignite UI CLI:<br /><code>ig add simple-combo newSimpleCombo</code><details>Basic IgxSimpleCombo sample.</details>                                                                                                                           | [IgxSimpleCombo](../../simple-combo.mdx) with single selection.                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
 | badge                           | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c badge newBadge</code><br />Ignite UI CLI:<br /><code>ig add badge newBadge</code><details>Basic IgxBadge sample.</details>                                                                                                                                                           | [IgxBadge](../../inputs/badge.mdx) displaying a status indicator.                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 | button-group                    | Ignite UI Schematics collection:<br /><code>ng g @igniteui/angular-schematics:c button-group newButtonGroup</code><br />Ignite UI CLI:<br /><code>ig add button-group newButtonGroup</code><details>Basic IgxButtonGroup sample.</details>                                                                                                                           | [IgxButtonGroup](../../inputs/button-group.mdx) with a set of toggle buttons.                                                                                                                                                                                                                                                                                                                                                                                                                                                           |

docs/angular/src/content/en/components/general/update-guide.mdx

@@ -1564,7 +1564,7 @@ The `ng update` process will update all enumeration names, like `AvatarType`, `T
     ```
 
 - IgxCombo
-  - The way that the [`igx-combo`](/combo) handles selection and data binding is changed.
+  - The way that the [`igx-combo`](/inputs/combo/overview) handles selection and data binding is changed.
 
   - If the combo's [`valueKey`] input is defined, the control will look for that specific property in the passed array of data items when performing selection.
     **All** selection events are handled with the value of the data items' `valueKey` property.
@@ -1603,7 +1603,7 @@ The `ng update` process will update all enumeration names, like `AvatarType`, `T
     }
     ```
 
-    You can read more about setting up the combo in the [readme](https://github.com/IgniteUI/igniteui-angular/blob/master/projects/igniteui-angular/src/lib/combo/README.md#value-binding) and in the [official documentation](/combo#selection-api).
+    You can read more about setting up the combo in the [readme](https://github.com/IgniteUI/igniteui-angular/blob/master/projects/igniteui-angular/src/lib/combo/README.md#value-binding) and in the [official documentation](/inputs/combo/overview#value-and-selection).
 
 ## From 8.0.x to 8.1.x
 

docs/angular/src/content/en/components/grids-and-lists.mdx

@@ -149,7 +149,7 @@ Full support for exporting data grids to XLSX, XLS, TSV or CSV. The Ignite UI fo
 - [Grid-level Searching](/grid/search)
 - [Export to Excel, CSV, TSV](/exporter-excel)
 - [Multi-Column Headers](/grid/multi-column-headers)
-- [Combo Box/Dropdown](/combo)
+- [Combo Box/Dropdown](/inputs/combo/overview)
 - [Virtualization and Performance](/grid/virtualization)
 - [Remote Data Load on Demand](/grid/virtualization#remote-virtualization)
 - [Cell Templates](/grid/grid#cell-template)

docs/angular/src/content/en/components/overlay-styling.mdx

@@ -18,7 +18,7 @@ import Sample from 'igniteui-astro-components/components/mdx/Sample.astro';
 <div class="highlight">
 
 
-[`IgxOverlayService`](/overlay) is used to display content above the page content. A lot of Ignite UI for Angular components use the overlay - [Drop Down](/drop-down), [Combo](/combo), [Date Picker](/date-picker) and more - so it is important to understand how the overlay displays content.
+[`IgxOverlayService`](/overlay) is used to display content above the page content. A lot of Ignite UI for Angular components use the overlay - [Drop Down](/drop-down), [Combo](/inputs/combo/overview), [Date Picker](/date-picker) and more - so it is important to understand how the overlay displays content.
 To display the content above other elements, the service moves it into a special outlet container (attached at the end of the document's body, by default). This behavior can affect styles [scoped to specific container](#scoped-overlay-styles).
 </div>
 <hr/>
@@ -53,7 +53,7 @@ Because these universal overrides are global, the drop-down content can consume
 
 A local theme can only affect overlay content that inherits from its container or matches its generated selectors. Content attached to the default outlet at the end of `body` is not a descendant of the component that opened it.
 
-For example, the `igx-combo` item [styles](/combo#styling) use the drop-down theme. This component-local theme takes effect after the combo outlet is moved beneath the host:
+For example, the `igx-combo` item [styles](/inputs/combo/overview#styling) use the drop-down theme. This component-local theme takes effect after the combo outlet is moved beneath the host:
 
 ```scss
 // overlay-styling.component.scss

docs/angular/src/content/en/components/simple-combo.mdx

@@ -13,7 +13,7 @@ import ApiLink from 'igniteui-astro-components/components/mdx/ApiLink.astro';
 
 # Angular Single Select ComboBox Component Overview
 
-The Angular Single Select ComboBox component is a modification of [ComboBox component](/combo) that allows single selection. We call it "simple combo". Due to high demand for single-selection mode for the original ComboBox component, we created an extension component which offers an editable search input that allows users to choose an option from a predefined list of items and to input custom values.
+The Angular Single Select ComboBox component is a modification of [ComboBox component](/inputs/combo/overview) that allows single selection. We call it "simple combo". Due to high demand for single-selection mode for the original ComboBox component, we created an extension component which offers an editable search input that allows users to choose an option from a predefined list of items and to input custom values.
 
 ## Angular Simple ComboBox Example
 

docs/angular/src/content/en/components/themes/roundness.mdx

@@ -20,7 +20,7 @@ Many Ignite UI components have predefined minimum and maximum border-radius valu
 When you set `--ig-radius-factor` to 0, the component uses its minimum border-radius and will appear more block-like with sharp corners. When set to 1, the component uses its maximum predefined border-radius and will appear rounded.
 
 Here is a list of the components that have predefined minimum and maximum border-radius values and can be modified using the `--ig-radius-factor` variable: <br/>
-• [Action Strip](/action-strip) • [Button](inputs/button) • [Button Group](/inputs/button-group) • [Calendar](/calendar) • [Card](/layouts/card) • [Carousel](/layouts/carousel) • [Checkbox](/inputs/checkbox) • [Chip](/inputs/chip) • [Combo](/combo) • [Date Picker](/date-picker) • [Date Range Picker](/date-range-picker) • [Grid](/grid/grid) • [Input Group](/input-group) • [Linear Progress](/linear-progress) • [List](/list) • [Month Picker](/month-picker) • [Navigation Drawer](/navdrawer) • [Radio](/inputs/radio) • [Ripple](/ripple) • [Snackbar](/snackbar) • [Switch](inputs/switch) • [Toast](/toast)
+• [Action Strip](/action-strip) • [Button](inputs/button) • [Button Group](/inputs/button-group) • [Calendar](/calendar) • [Card](/layouts/card) • [Carousel](/layouts/carousel) • [Checkbox](/inputs/checkbox) • [Chip](/inputs/chip) • [Combo](/inputs/combo/overview) • [Date Picker](/date-picker) • [Date Range Picker](/date-range-picker) • [Grid](/grid/grid) • [Input Group](/input-group) • [Linear Progress](/linear-progress) • [List](/list) • [Month Picker](/month-picker) • [Navigation Drawer](/navdrawer) • [Radio](/inputs/radio) • [Ripple](/ripple) • [Snackbar](/snackbar) • [Switch](inputs/switch) • [Toast](/toast)
 
 ## Usage
 

docs/angular/src/content/en/components/toc.json

@@ -1321,8 +1321,8 @@
   },
   {
     "name": "Combo",
-    "href": "combo.mdx",
-    "new": false,
+    "href": "inputs/combo/overview.mdx",
+    "updated": true,
     "items": [
       {
         "name": "Features",

docs/angular/src/content/en/grids_templates/cascading-combos.mdx

@@ -11,7 +11,7 @@ import ApiLink from 'igniteui-astro-components/components/mdx/ApiLink.astro';
 
 # Angular Grid with Cascading Combos
 
-The Grid's Editing functionality provides with the opportunity to use [Cascading Combos](/simple-combo#cascading-scenario). By selecting the value in any preceding [Combos](/combo), the users will receive only the data that is relevant to their selection within the next Combo.
+The Grid's Editing functionality provides with the opportunity to use [Cascading Combos](/simple-combo#cascading-scenario). By selecting the value in any preceding [Combos](/inputs/combo/overview), the users will receive only the data that is relevant to their selection within the next Combo.
 
 ## Angular Grid with Cascading Combos Sample Overview
 

docs/angular/src/content/en/grids_templates/cell-editing.mdx

@@ -64,7 +64,7 @@ Ignite UI for Angular {ComponentTitle} component provides powerful data manipula
 </ComponentBlock>
 
 <DocsAside type="info">
-By using `igxCellEditor` with any type of editor component, the keyboard navigation flow will be disrupted. The same applies to direct editing of the custom cell that enters edit mode. This is because the `focus` will remain on the `cell element`, not on the editor component that we've added - [`igxSelect`](/select), [`igxCombo`](/combo), etc. This is why we should take leverage of the `igxFocus` directive, which will move the focus directly in the in-cell component and will preserve `a fluent editing flow` of the cell/row.
+By using `igxCellEditor` with any type of editor component, the keyboard navigation flow will be disrupted. The same applies to direct editing of the custom cell that enters edit mode. This is because the `focus` will remain on the `cell element`, not on the editor component that we've added - [`igxSelect`](/select), [`igxCombo`](/inputs/combo/overview), etc. This is why we should take leverage of the `igxFocus` directive, which will move the focus directly in the in-cell component and will preserve `a fluent editing flow` of the cell/row.
 </DocsAside>
 
 ## Cell Editing
@@ -199,7 +199,7 @@ The cell editing template directive `igxCellEditor`, handles how a column's cell
 </DocsAside>
 
 <DocsAside type="info">
-By using `igxCellEditor` with any type of editor component, the keyboard navigation flow will be disrupted. The same applies to direct editing of the custom cell that enters edit mode. This is because the `focus` will remain on the `cell element`, not on the editor component that we've added - [`igxSelect`](/select), [`igxCombo`](/combo), etc. This is why we should take leverage of the `igxFocus` directive, which will move the focus directly in the in-cell component and will preserve `a fluent editing flow` of the cell/row.
+By using `igxCellEditor` with any type of editor component, the keyboard navigation flow will be disrupted. The same applies to direct editing of the custom cell that enters edit mode. This is because the `focus` will remain on the `cell element`, not on the editor component that we've added - [`igxSelect`](/select), [`igxCombo`](/inputs/combo/overview), etc. This is why we should take leverage of the `igxFocus` directive, which will move the focus directly in the in-cell component and will preserve `a fluent editing flow` of the cell/row.
 </DocsAside>