syncfusion-content · Karthick-Arjunan · Sep 3, 2026 · Sep 3, 2026
diff --git a/uwp/Docking/Auto-Hide-Window.md b/uwp/Docking/Auto-Hide-Window.md
@@ -7,16 +7,16 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Auto Hide Window in UWP SfDockingManager
+# Auto Hide Window in UWP Docking Control
 
-`AutoHide` window is one of the states in the `SfDockingManager`. To enable Auto hidden for `SfDockingManager`'s children, set the `SfDockingManager` child `DockState` value as `AutoHidden`.
+`AutoHide` is one of the window states supported by the `UWP Docking Control`. To enable the `AutoHide` state for a child window, set its `DockState` property to `AutoHidden`.
 
 ![Auto-Hide-Window-img1](Auto-Hide-Window-images/Auto-Hide-Window-img1.jpeg)
 
 
 ## Configuring Window in Different Sides
 
-`AutoHidden` window can be placed in four different sides such as Top, Bottom, Left and Right. To place the four auto hidden children in four different sides, set the `SideInDockedMode` property according to its corresponding values in the `SfDockingManager`.
+`AutoHidden` window can be placed in four different sides such as Top, Bottom, Left and Right. To place the four auto hidden children in four different sides, set the `SideInDockedMode` property according to its corresponding values in the `UWP Docking Control`.
 
 {% tabs %}
 
@@ -51,7 +51,7 @@ documentation: ug
 
 ## Side Panel and TabItem Customization
 
-The side panel and side panel header can be customized through `SidePanelBackground`, `SidePanelItemsBackground` and `SidePanelItemsForeground` properties of the `SfDockingManager`.
+The side panel and side panel header can be customized through `SidePanelBackground`, `SidePanelItemsBackground` and `SidePanelItemsForeground` properties of the `UWP Docking Control`.
 
 {% tabs %}
 
@@ -99,7 +99,7 @@ The animation speed while auto hiding a window can be configured by setting the
 
 ## Applying Different Animations for AutoHide Window
 
-`SfDockingManager` supports three different built-in animations while auto-hiding the windows such as Fade, Scale and Slide, which can be set through the `AutoHideAnimationMode` property.
+`UWP Docking Control` supports three different built-in animations while auto-hiding the windows such as Fade, Scale and Slide, which can be set through the `AutoHideAnimationMode` property.
 
 `Fade` – AutoHidden window fades while auto hiding.
 
@@ -173,7 +173,7 @@ The Pin button, which performs the Auto Hide functionality, is visible by defaul
 ![Auto-Hide-Window-img4](Auto-Hide-Window-images/Auto-Hide-Window-img4.jpeg)
 
 
-To show or collapse the AutoHide button for a specific child in the `SfDockingManager`, the `IsPinButtonVisible` attached property can be used. By default, the `IsPinButtonVisible` value is true. This functionality can be disabled by setting its value as false.
+To show or collapse the AutoHide button for a specific child in the `UWP Docking Control`, the `IsPinButtonVisible` attached property can be used. By default, the `IsPinButtonVisible` value is true. This functionality can be disabled by setting its value as false.
 
 {% tabs %}
 
@@ -196,7 +196,7 @@ To show or collapse the AutoHide button for a specific child in the `SfDockingMa
 ![Auto-Hide-Window-img5](Auto-Hide-Window-images/Auto-Hide-Window-img5.jpeg)
 
 
-To enable or disable the AutoHide functionality for a specific child in the `SfDockingManager`, the `CanAutoHide` attached property can be used. By default, the `CanAutoHide` value is true. This functionality can be disabled by setting its value as false.
+To enable or disable the AutoHide functionality for a specific child in the `UWP Docking Control`, the `CanAutoHide` attached property can be used. By default, the `CanAutoHide` value is true. This functionality can be disabled by setting its value as false.
 
 {% tabs %}
 

diff --git a/uwp/Docking/Dealing-with-Windows.md b/uwp/Docking/Dealing-with-Windows.md
@@ -7,11 +7,11 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Dealing with Windows in UWP SfDockingManager
+# Dealing with Windows in UWP Docking Control
 
 ## Activating a window
 
-A particular child window can be activated in `SfDockingManager` using its name or instance reference through the property `ActiveWindow` and `ActivateWindow` method that passes the element as argument to activate.
+A particular child window can be activated in `UWP Docking Control` using its name or instance reference through the property `ActiveWindow` and `ActivateWindow` method that passes the element as argument to activate.
 
 {% tabs %}
 
@@ -72,9 +72,9 @@ docking.ActivateWindow(SolutionExplorer);
 
 ## Adding Window Programmatically
 
-Any UI element can be added inside the `SfDockingManager` as its child windows. The windows are added as Dock windows, since the default value of the `DockState` is Dock. The UI element is added in the `SfDockingManager` using the Add method of the `DockItems` property of the `SfDockingManager`.
+The `UWP Docking Control` supports hosting any UI element as a child window. By default, child windows are added as docked windows because the `DockState` property is set to Dock. UI elements can be added using the `Add` method of the `DockItems` collection.
 
-For example, `ContentControl` is added as a window for `SfDockingManager`.
+For example, `ContentControl` is added as a window for `UWP Docking Control`.
 
 {% tabs %}
 
@@ -125,7 +125,7 @@ DockingManager1.DockItems.Add(content5);
 
 ## Hiding Window Programmatically
 
-To hide the window, set the `DockState` attached property of the `SfDockingManager` as `Hidden`.
+To hide the window, set the `DockState` attached property of the `UWP Docking Control` as `Hidden`.
 
 {% tabs %}
 
@@ -167,7 +167,7 @@ A Docking window can be customized using the property `DockWindowCaptionBackgrou
 
 ## Customizing Active Docking Window
 
-Active docking window can be customized using the property `DockWindowActiveForeground`, `DockWindowActiveBackground` with desired brush values.
+Active Docking window can be customized using the property `DockWindowActiveForeground`, `DockWindowActiveBackground` with desired brush values.
 
 {% tabs %}
 
@@ -217,7 +217,7 @@ ForeColor and BackColor of Inactive document window can be customized using the
 
 ## Customizing Selected Document window
 
-Selected Document window can be customized using the property `DocumentTabItemSelectedBackground`, `DocumentTabItemSelectedForeground` with desired brush values. Font size of the selected document window can be customized through `DocumentTabItemSelectedFontSize` property of DockingManager.
+Selected Document window can be customized using the property `DocumentTabItemSelectedBackground`, `DocumentTabItemSelectedForeground` with desired brush values. Font size of the selected document window can be customized through `DocumentTabItemSelectedFontSize` property of UWP Docking Control.
 
 {% tabs %}
 
@@ -266,7 +266,7 @@ The float window can be customized by setting `FloatWindowBackground`, `FloatWin
 ![Customized float window in Docking Manager](Dealing-with-Windows-images/Dealing-with-Windows-img6.jpeg)
 
 
-## Handling state change of DockingManager child element
+## Handling state change of UWP Docking Control child element
 
 The `DockStateChanging` event will be raised whenever the child element is changing its State. The state change of a child element can now be restricted by setting `args.Cancel` to true. "args" represents the event argument of `DockStateChangingEventArgs` for the `DockStateChanging` event. The default value of `args.Cancel` is false.
 
@@ -310,7 +310,7 @@ args.Cancel = true;
 
 {% endtabs %}
 
-## Restricting DockingManager child element from being closed
+## Restricting UWP Docking Control child element from being closed
 
 The state of the child element will change to `Hidden` while closing it. It can be restricted by changing the value of `args.Cancel` to true. The following code describes how to handle the closing of a child using the `DockStateChanging` event.
 
@@ -392,9 +392,9 @@ The fill color of hint shadow/dock preview element can be customized using `Dock
 ![Customized docking hint shadow color in Docking Manager](Dealing-with-Windows-images/Dealing-with-Windows-img8.jpeg)
 
 
-## Sizing Docking Windows
+## Sizing UWP Docking Windows
 
-`SfDockingManager` allows to set the desired width and height for the docking windows. 
+`UWP Docking Control` allows to set the desired width and height for the docking windows. 
 
 The desired height and width can be set for the Dock windows through the AttachedProperty `DesiredWidthInDockedMode` and `DesiredHeightInDockedMode` with the desired values.
 
@@ -419,7 +419,7 @@ The desired height and width can be set for the Dock windows through the Attache
 
 ## Occupy Whole Window
 
-To arrange the dock windows to a whole available space in the `SfDockingManager`, set `DockFill` property of `SfDockingManager` as true.
+To arrange the dock windows to a whole available space in the `UWP Docking Control`, set `DockFill` property of `SfDockingManager` as true.
 
 {% tabs %}
 
@@ -440,7 +440,7 @@ To arrange the dock windows to a whole available space in the `SfDockingManager`
 
 ## Enable/Disable ContextMenus
 
-`SfDockingManager` provides ContextMenu's for docking, floating, auto hiding and document windows. 
+`UWP Docking Control` provides ContextMenu's for docking, floating, auto hiding and document windows. 
 
 ### Enable/Disable context menu for docking, floating, auto hiding windows
 

diff --git a/uwp/Docking/Docking-Window.md b/uwp/Docking/Docking-Window.md
@@ -7,9 +7,9 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Docking Window in UWP SfDockingManager
+# Docking Window in UWP Docking Control
 
-Docking window is one of the states of `SfDockingManager`. Since Dock is the default value, initially all the children stay as Docking Window.
+Docking window is one of the states of `UWP Docking Control`. Since Dock is the default value, initially all the children stay as Docking Window.
 
 ![Docking-Window-img1](Docking-Window-images/Docking-Window-img1.jpeg)
 
@@ -24,7 +24,7 @@ The Five sides where the children can be docked are
 * Bottom
 * Tabbed
 
-To dock four children of `SfDockingManager` to each side, set the `SideInDockedMode` property with appropriate values.
+To dock four children of `UWP Docking Control` to each side, set the `SideInDockedMode` property with appropriate values.
 
 {% tabs %}
 
@@ -57,7 +57,7 @@ To dock four children of `SfDockingManager` to each side, set the `SideInDockedM
 
 A Docking window can be docked on any side of the Target Docking Window using an attached property named `TargetNameInDockedMode`.
 
-To set the child window as a TabbedWindow, the window should be aware of a Target window name. The following code helps to arrange children of `SfDockingManager` that target a single Docking window docked along Left, Top, Right and Tabbed.
+To set the child window as a TabbedWindow, the window should be aware of a Target window name. The following code helps to arrange children of `UWP Docking Control` that target a single Docking window docked along Left, Top, Right and Tabbed.
 
 {% tabs %}
 

diff --git a/uwp/Docking/Document-Windows.md b/uwp/Docking/Document-Windows.md
@@ -7,9 +7,9 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Document Window in UWP SfDockingManager
+# Document Window in UWP Docking Control
 
-Document window is one of the states available in the `SfDockingManager`. To make the children of the `SfDockingManager` as Document, set the child's `DockState` value as `Document`.
+Document is one of the window states supported by the` UWP Docking Control`. To display a child window in the document area, set its `DockState` property to `Document`.
 
 All the Document windows are added in a `DocumentContainer`. Content can be switched by clicking the item header or choosing item from TabStripMenu.
 
@@ -34,7 +34,7 @@ When the `DockFill` property is set to true, dock windows are allowed to occupy
 
 ## Specify Placement for Document Window
 
-A Document window can be added either at the start or end index position in the `DocumentContainer` by setting the `DocumentTabItemPlacement` property of the `SfDockingManager`. The `DocumentTabItemPlacement` enumeration values are `Start` and `End`; the default value is `Start`.
+A Document window can be added either at the start or end index position in the `DocumentContainer` by setting the `DocumentTabItemPlacement` property of the `UWP Docking Control`. The `DocumentTabItemPlacement` enumeration values are `Start` and `End`; the default value is `Start`.
 
 * Adding Documents at Start position
 

diff --git a/uwp/Docking/Floating-Window.md b/uwp/Docking/Floating-Window.md
@@ -7,9 +7,9 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Floating Window in UWP SfDockingManager
+# Floating Window in UWP Docking Control
 
-Floating window is one of the states in the `SfDockingManager`. To make children of the `SfDockingManager` as Float, set the `SfDockingManager` child’s `DockState` values as Float.
+Float is one of the window states supported by the `UWP Docking Control`. To display a child window as a floating window, set its `DockState` property to `Float`.
 
 {% tabs %}
 
@@ -74,7 +74,7 @@ SfDockingManager.SetSideInDockedMode(ErrorList, Dock.Top);
 
 ## Positioning on Desired Location
 
-The `FloatWindow` can be placed at any desired location. To position the `FloatWindow` at the desired location with the required rectangle bounds, invoke the `SetFloatingWindowRect` method of the `SfDockingManager`.
+The `FloatWindow` can be placed at any desired location. To position the `FloatWindow` at the desired location with the required rectangle bounds, invoke the `SetFloatingWindowRect` method of the `UWP Docking Control`.
 
 {% tabs %}
 

diff --git a/uwp/Docking/Getting-Started.md b/uwp/Docking/Getting-Started.md
@@ -7,13 +7,13 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Getting Started with UWP SfDockingManager
+# Getting Started with UWP Docking Control
 
-This section explains how to implement a similar UI as Visual Studio using the `SfDockingManager`.
+This section explains how to implement a similar UI as Visual Studio using the `UWP Docking Control`.
 
-## Add SfDockingManager
+## Add UWP Docking Control
 
-There are several ways to add Syncfusion control in to the Visual Studio UWP project. The following will help to add a `SfDockingManager` control through XAML Code.
+There are several ways to add Syncfusion control in to the Visual Studio UWP project. The following will help to add a `UWP Docking Control` control through XAML Code.
 
 * Create a UWP project in Visual Studio and refer to the following assemblies.
 
@@ -44,7 +44,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout">
 
 {% endtabs %}
 
-* Now add the `SfDockingManager` control with a required optimal name by using the included namespace.
+* Now add the `UWP Docking Control` control with a required optimal name by using the included namespace.
 
 {% tabs %}
 
@@ -58,7 +58,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout">
 
 ## Add Children to SfDockingManager
 
-`SfDockingManager` can accept any control as its children. Here five ContentControls have been added as the children of the `SfDockingManager`.
+The `UWP Docking Control` can host any control as a child window. In the following example, five ContentControl elements are added as child windows.
 
 {% tabs %}
 
@@ -87,7 +87,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout">
 
 ## Set Header for the Children
 
-`SfDockingManager` provides an attached property `Header`, that helps to set the header for a child window. Set the Header Property value as “Solution Explorer” for the first child and repeat the same procedure for the remaining children with values "ToolBox", "Properties", "Output" and "Start Page".
+`UWP Docking Control` provides an attached property `Header`, that helps to set the header for a child window. Set the Header Property value as “Solution Explorer” for the first child and repeat the same procedure for the remaining children with values "ToolBox", "Properties", "Output" and "Start Page".
 
 {% tabs %}
 
@@ -116,7 +116,7 @@ xmlns:layout="using:Syncfusion.UI.Xaml.Controls.Layout">
 
 ## Set State for the Children
 
-`SfDockingManager` provides an attached property `DockState`, that helps to set the State of child windows. Since Dock is the default value of DockState, initially all the children will stay as Docking Window.
+`UWP Docking Control` provides an attached property `DockState`, that helps to set the State of child windows. Since Dock is the default value of DockState, initially all the children will stay as Docking Window.
 
 To Auto hide the “ToolBox” window, set its `DockState` property as `AutoHidden`. Repeat the same procedure with the `DockState` value as Float and Document for “Properties” and “Start Page” windows respectively to make them as Floating Window and Document Window.
 
@@ -147,7 +147,7 @@ To Auto hide the “ToolBox” window, set its `DockState` property as `AutoHidd
 
 ## Set Sides for the Children
 
-`SfDockingManager` provides an attached property `SideInDockedMode`, that helps to dock a window at the required side. Since Left is the default value, initially all the windows are docked to left side.
+`UWP Docking Control` provides an attached property `SideInDockedMode`, that helps to dock a window at the required side. Since Left is the default value, initially all the windows are docked to left side.
 
 Set the `SideInDockedMode` value as Right for “Solution Explorer” window to dock it on the right side.
 

diff --git a/uwp/Docking/Nested-DockingManager.md b/uwp/Docking/Nested-DockingManager.md
@@ -7,9 +7,9 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# Nested DockingManager in UWP SfDockingManager
+# Nested DockingManager in UWP Docking Control
 
-`SfDockingManager` provides the Nested DockingManager support, which allows adding `SfDockingManager` as a child window to another `SfDockingManager`.
+The `UWP Docking Control` provides nested docking support, enabling it to be hosted as a child window within another `UWP Docking Control`.
 
 {% tabs %}
 

diff --git a/uwp/Docking/Overview.md b/uwp/Docking/Overview.md
@@ -7,16 +7,16 @@ control: SfDockingManager
 documentation: ug
 ---
 
-# About Syncfusion® UWP SfDockingManager Control
+# About Syncfusion® UWP Docking Control
 
-The `SfDockingManager` control implements an architecture, that allows child controls to be docked at any part of a page as in Microsoft Visual Studio. The dock panels containing the child elements can be interactively dragged to any area within the page. These windows can also be floated, tabbed, and auto hidden at runtime.
+The `UWP Docking Control` implements an architecture, that allows child controls to be docked at any part of a page as in Microsoft Visual Studio. The dock panels containing the child elements can be interactively dragged to any area within the page. These windows can also be floated, tabbed, and auto hidden at runtime.
 
 ## Features
 
-* `SfDockingManager` supports different dock states such as [Docking](https://help.syncfusion.com/uwp/docking/docking-window), [Floating](https://help.syncfusion.com/uwp/docking/floating-window), [AutoHide](https://help.syncfusion.com/uwp/docking/auto-hide-window) and [Document](https://help.syncfusion.com/uwp/docking/document-windows).
-* [Tabbed Document Interface(TDI)](https://help.syncfusion.com/uwp/docking/tabbed-window) is available in `SfDockingManager`.
+* `UWP Docking Control` supports different dock states such as [Docking](https://help.syncfusion.com/uwp/docking/docking-window), [Floating](https://help.syncfusion.com/uwp/docking/floating-window), [AutoHide](https://help.syncfusion.com/uwp/docking/auto-hide-window) and [Document](https://help.syncfusion.com/uwp/docking/document-windows).
+* [Tabbed Document Interface(TDI)](https://help.syncfusion.com/uwp/docking/tabbed-window) is available in `UWP Docking Control`.
 * Built-in support for TabList ContextMenu and TabItem ContextMenu.
-* `SfDockingManager` supports all possible ways to dock the elements.
+* `UWP Docking Control` supports all possible ways to dock the elements.
 * Support for resizing Splitters.
 * Different types of auto hide animation such as Fade, Scale and Slide.
 * ToolTip support for all default buttons.