Link to W version pages in window creation

sdk-api-src/content/psapi/nc-psapi-penum_page_file_callbackw.md

@@ -53,7 +53,7 @@ api_name:
 ## -description
 
 An application-defined callback function used with the 
-<a href="/windows/desktop/api/psapi/nf-psapi-enumpagefilesa">EnumPageFiles</a> function.
+<a href="/windows/desktop/api/psapi/nf-psapi-enumpagefilesw">EnumPageFiles</a> function.
 
 The <b>PENUM_PAGE_FILE_CALLBACK</b> type defines a pointer to this callback function. 
 <b>EnumPageFilesProc</b> is a placeholder for the application-defined function name.
@@ -63,7 +63,7 @@ The <b>PENUM_PAGE_FILE_CALLBACK</b> type defines a pointer to this callback func
 ### -param pContext [in]
 
 The user-defined data passed from 
-<a href="/windows/desktop/api/psapi/nf-psapi-enumpagefilesa">EnumPageFiles</a>.
+<a href="/windows/desktop/api/psapi/nf-psapi-enumpagefilesw">EnumPageFiles</a>.
 
 ### -param pPageFileInfo [in]
 
@@ -86,7 +86,7 @@ To stop enumeration, the callback function must return FALSE.
 
 
 
-<a href="/windows/desktop/api/psapi/nf-psapi-enumpagefilesa">EnumPageFiles</a>
+<a href="/windows/desktop/api/psapi/nf-psapi-enumpagefilesw">EnumPageFiles</a>
 
 
 

sdk-api-src/content/psapi/nf-psapi-getmodulebasenamew.md

@@ -96,14 +96,14 @@ The <b>GetModuleBaseName</b> function is primarily designed for use by debuggers
 
 
 
-To retrieve the base name of a module in the current process, use the <a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-getmodulefilenamea">GetModuleFileName</a> function to retrieve the full module name and then use a function call such as <code>strrchr(szmodulename, '\\')</code> to scan to the beginning of the base name within the module name string. This is more efficient and more reliable than calling  <b>GetModuleBaseName</b>  with a handle to the current process.
+To retrieve the base name of a module in the current process, use the <a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-getmodulefilenamew">GetModuleFileName</a> function to retrieve the full module name and then use a function call such as <code>strrchr(szmodulename, '\\')</code> to scan to the beginning of the base name within the module name string. This is more efficient and more reliable than calling  <b>GetModuleBaseName</b>  with a handle to the current process.
 
 
 
-To retrieve the base name of the main executable module for a remote process, use the <a href="/windows/desktop/api/psapi/nf-psapi-getprocessimagefilenamea">GetProcessImageFileName</a> or <a href="/windows/desktop/api/winbase/nf-winbase-queryfullprocessimagenamea">QueryFullProcessImageName</a> function to retrieve the module name and then use the <code>strrchr</code> function as described in the previous paragraph. This is more efficient and more reliable than calling  <b>GetModuleBaseName</b>  with a NULL module handle.
+To retrieve the base name of the main executable module for a remote process, use the <a href="/windows/desktop/api/psapi/nf-psapi-getprocessimagefilenamew">GetProcessImageFileName</a> or <a href="/windows/desktop/api/winbase/nf-winbase-queryfullprocessimagenamew">QueryFullProcessImageName</a> function to retrieve the module name and then use the <code>strrchr</code> function as described in the previous paragraph. This is more efficient and more reliable than calling  <b>GetModuleBaseName</b>  with a NULL module handle.
 
 
-The <b>GetModuleBaseName</b> function does not retrieve the base name for modules that were loaded with the <b>LOAD_LIBRARY_AS_DATAFILE</b> flag. For more information, see <a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexa">LoadLibraryEx</a>.
+The <b>GetModuleBaseName</b> function does not retrieve the base name for modules that were loaded with the <b>LOAD_LIBRARY_AS_DATAFILE</b> flag. For more information, see <a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryexw">LoadLibraryEx</a>.
 
 Starting with Windows 7 and Windows Server 2008 R2, Psapi.h establishes 
     version numbers for the PSAPI functions. The PSAPI version number affects the name used to call the function and 
@@ -142,7 +142,7 @@ For an example, see
 
 
 
-<a href="/windows/desktop/api/psapi/nf-psapi-getmodulefilenameexa">GetModuleFileNameEx</a>
+<a href="/windows/desktop/api/psapi/nf-psapi-getmodulefilenameexw">GetModuleFileNameEx</a>
 
 
 

sdk-api-src/content/psapi/nf-psapi-getmodulefilenameexw.md

@@ -151,7 +151,7 @@ For an example, see
 
 
 
-<a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibrarya">LoadLibrary</a>
+<a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-loadlibraryw">LoadLibrary</a>
 
 
 

sdk-api-src/content/psapi/nf-psapi-getprocessimagefilenamew.md

@@ -92,9 +92,9 @@ The <b>GetProcessImageFileName</b> function returns the path in device form, rat
 
 \Device\Harddisk0\Partition1\Windows\System32\Ctype.nls
 
-To retrieve the module name of the current process, use the <a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-getmodulefilenamea">GetModuleFileName</a> function with a NULL module handle. This is more efficient than calling the <b>GetProcessImageFileName</b> function with a handle to the current process.
+To retrieve the module name of the current process, use the <a href="/windows/desktop/api/libloaderapi/nf-libloaderapi-getmodulefilenamew">GetModuleFileName</a> function with a NULL module handle. This is more efficient than calling the <b>GetProcessImageFileName</b> function with a handle to the current process.
 
-To retrieve the name of the main executable module for a remote process in win32 path format, use the <a href="/windows/desktop/api/winbase/nf-winbase-queryfullprocessimagenamea">QueryFullProcessImageName</a> function.
+To retrieve the name of the main executable module for a remote process in win32 path format, use the <a href="/windows/desktop/api/winbase/nf-winbase-queryfullprocessimagenamew">QueryFullProcessImageName</a> function.
 
 Starting with Windows 7 and Windows Server 2008 R2, Psapi.h establishes 
     version numbers for the PSAPI functions. The PSAPI version number affects the name used to call the function and 
@@ -130,4 +130,4 @@ Programs that must run on earlier versions of Windows as
 
 
 
-<a href="/windows/desktop/api/winbase/nf-winbase-queryfullprocessimagenamea">QueryFullProcessImageName</a>
+<a href="/windows/desktop/api/winbase/nf-winbase-queryfullprocessimagenamew">QueryFullProcessImageName</a>

sdk-api-src/content/winuser/nf-winuser-createwindowexw.md

@@ -63,7 +63,7 @@ req.apiset: ext-ms-win-ntuser-window-l1-1-0 (introduced in Windows 8)
 
 ## -description
 
-Creates an overlapped, pop-up, or child window with an extended window style; otherwise, this function is identical to the <a href="/windows/desktop/api/winuser/nf-winuser-createwindowa">CreateWindow</a> function. For more information about creating a window and for full descriptions of the other parameters of <b>CreateWindowEx</b>, see <b>CreateWindow</b>.
+Creates an overlapped, pop-up, or child window with an extended window style; otherwise, this function is identical to the <a href="/windows/desktop/api/winuser/nf-winuser-createwindoww">CreateWindow</a> function. For more information about creating a window and for full descriptions of the other parameters of <b>CreateWindowEx</b>, see <b>CreateWindow</b>.
 
 ## -parameters
 
@@ -79,15 +79,15 @@ Type: <b>LPCTSTR</b>
 
 A <b>null</b>-terminated string or a class atom.
 
-If a <b>null</b>-terminated string, it specifies the window class name. The class name can be any name registered with the <a href="/windows/desktop/api/winuser/nf-winuser-registerclasswa">RegisterClass</a> or <a href="/windows/desktop/api/winuser/nf-winuser-registerclassexa">RegisterClassEx</a> function, provided that the module that registers the class is also the module that creates the window. The class name can also be any of the predefined <a href="/windows/desktop/winmsg/about-window-classes">system class</a> names.
+If a <b>null</b>-terminated string, it specifies the window class name. The class name can be any name registered with the <a href="/windows/desktop/api/winuser/nf-winuser-registerclassw">RegisterClass</a> or <a href="/windows/desktop/api/winuser/nf-winuser-registerclassexw">RegisterClassEx</a> function, provided that the module that registers the class is also the module that creates the window. The class name can also be any of the predefined <a href="/windows/desktop/winmsg/about-window-classes">system class</a> names.
 
 If a class atom created by a previous call to <b>RegisterClass</b> or <b>RegisterClassEx</b>, it must be converted using the macro <a href="/windows/desktop/api/winbase/nf-winbase-makeintatom">MAKEINTATOM</a>. (The atom must be in the low-order word of <i>lpClassName</i>; the high-order word must be zero.)
 
 ### -param lpWindowName [in, optional]
 
 Type: <b>LPCTSTR</b>
 
-The window name. If the window style specifies a title bar, the window title pointed to by <i>lpWindowName</i> is displayed in the title bar. When using <a href="/windows/desktop/api/winuser/nf-winuser-createwindowa">CreateWindow</a> to create controls, such as buttons, check boxes, and static controls, use <i>lpWindowName</i> to specify the text of the control. When creating a static control with the <b>SS_ICON</b> style, use <i>lpWindowName</i> to specify the icon name or identifier. To specify an identifier, use the syntax "#<i>num</i>".
+The window name. If the window style specifies a title bar, the window title pointed to by <i>lpWindowName</i> is displayed in the title bar. When using <a href="/windows/desktop/api/winuser/nf-winuser-createwindoww">CreateWindow</a> to create controls, such as buttons, check boxes, and static controls, use <i>lpWindowName</i> to specify the text of the control. When creating a static control with the <b>SS_ICON</b> style, use <i>lpWindowName</i> to specify the icon name or identifier. To specify an identifier, use the syntax "#<i>num</i>".
 
 ### -param dwStyle [in]
 
@@ -146,9 +146,9 @@ A handle to the instance of the module to be associated with the window.
 
 Type: <b>LPVOID</b>
 
-Pointer to a value to be passed to the window through the <a href="/windows/desktop/api/winuser/ns-winuser-createstructa">CREATESTRUCT</a> structure (<b>lpCreateParams</b> member) pointed to by the <i>lParam</i> param of the <b>WM_CREATE</b> message.  This message is sent to the created window by this function before it returns.
+Pointer to a value to be passed to the window through the <a href="/windows/desktop/api/winuser/ns-winuser-createstructw">CREATESTRUCT</a> structure (<b>lpCreateParams</b> member) pointed to by the <i>lParam</i> param of the <b>WM_CREATE</b> message.  This message is sent to the created window by this function before it returns.
 
-If an application calls <a href="/windows/desktop/api/winuser/nf-winuser-createwindowa">CreateWindow</a> to create a MDI client window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-clientcreatestruct">CLIENTCREATESTRUCT</a> structure. If an MDI client window calls <b>CreateWindow</b> to create an MDI child window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-mdicreatestructa">MDICREATESTRUCT</a> structure. <i>lpParam</i> may be <b>NULL</b> if no additional data is needed.
+If an application calls <a href="/windows/desktop/api/winuser/nf-winuser-createwindoww">CreateWindow</a> to create a MDI client window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-clientcreatestruct">CLIENTCREATESTRUCT</a> structure. If an MDI client window calls <b>CreateWindow</b> to create an MDI child window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-mdicreatestructw">MDICREATESTRUCT</a> structure. <i>lpParam</i> may be <b>NULL</b> if no additional data is needed.
 
 ## -returns
 
@@ -318,15 +318,15 @@ BOOL Create(
 
 
 
-<a href="/windows/desktop/api/winuser/ns-winuser-createstructa">CREATESTRUCT</a>
+<a href="/windows/desktop/api/winuser/ns-winuser-createstructw">CREATESTRUCT</a>
 
 
 
 <b>Conceptual</b>
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-createwindowa">CreateWindow</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-createwindoww">CreateWindow</a>
 
 
 
@@ -346,11 +346,11 @@ BOOL Create(
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-registerclassa">RegisterClass</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-registerclassw">RegisterClass</a>
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-registerclassexa">RegisterClassEx</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-registerclassexw">RegisterClassEx</a>
 
 
 
@@ -362,7 +362,7 @@ BOOL Create(
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-setwindowlonga">SetWindowLong</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-setwindowlongw">SetWindowLong</a>
 
 
 

sdk-api-src/content/winuser/nf-winuser-createwindoww.md

@@ -54,7 +54,7 @@ api_name:
 
 Creates an overlapped, pop-up, or child window. It specifies the window class, window title, window style, and (optionally) the initial position and size of the window. The function also specifies the window's parent or owner, if any, and the window's menu.
 
-To use extended window styles in addition to the styles supported by <b>CreateWindow</b>, use the <a href="/windows/desktop/api/winuser/nf-winuser-createwindowexa">CreateWindowEx</a> function.
+To use extended window styles in addition to the styles supported by <b>CreateWindow</b>, use the <a href="/windows/desktop/api/winuser/nf-winuser-createwindowexw">CreateWindowEx</a> function.
 
 ## -syntax
 
@@ -80,7 +80,7 @@ HWND CreateWindowW(
 
 Type: <b>LPCWSTR</b>
 
-A <b>null</b>-terminated string or a class atom created by a previous call to the <a href="/windows/desktop/api/winuser/nf-winuser-registerclassa">RegisterClass</a> or <a href="/windows/desktop/api/winuser/nf-winuser-registerclassexa">RegisterClassEx</a> function. The atom must be in the low-order word of <i>lpClassName</i>; the high-order word must be zero. If <i>lpClassName</i> is a string, it specifies the window class name. The class name can be any name registered with <b>RegisterClass</b> or <b>RegisterClassEx</b>, provided that the module that registers the class is also the module that creates the window. The class name can also be any of the predefined system class names. For a list of system class names, see the Remarks section.
+A <b>null</b>-terminated string or a class atom created by a previous call to the <a href="/windows/desktop/api/winuser/nf-winuser-registerclassw">RegisterClass</a> or <a href="/windows/desktop/api/winuser/nf-winuser-registerclassexw">RegisterClassEx</a> function. The atom must be in the low-order word of <i>lpClassName</i>; the high-order word must be zero. If <i>lpClassName</i> is a string, it specifies the window class name. The class name can be any name registered with <b>RegisterClass</b> or <b>RegisterClassEx</b>, provided that the module that registers the class is also the module that creates the window. The class name can also be any of the predefined system class names. For a list of system class names, see the Remarks section.
 
 ### -param lpWindowName [in, optional]
 
@@ -145,9 +145,9 @@ A handle to the instance of the module to be associated with the window.
 
 Type: <b>LPVOID</b>
 
-A pointer to a value to be passed to the window through the <a href="/windows/desktop/api/winuser/ns-winuser-createstructa">CREATESTRUCT</a> structure (<b>lpCreateParams</b> member) pointed to by the <i>lParam</i> param of the <a href="/windows/desktop/winmsg/wm-create">WM_CREATE</a> message.  This message is sent to the created window by this function before it returns.
+A pointer to a value to be passed to the window through the <a href="/windows/desktop/api/winuser/ns-winuser-createstructw">CREATESTRUCT</a> structure (<b>lpCreateParams</b> member) pointed to by the <i>lParam</i> param of the <a href="/windows/desktop/winmsg/wm-create">WM_CREATE</a> message.  This message is sent to the created window by this function before it returns.
 
-If an application calls <b>CreateWindow</b> to create a MDI client window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-clientcreatestruct">CLIENTCREATESTRUCT</a> structure. If an MDI client window calls <b>CreateWindow</b> to create an MDI child window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-mdicreatestructa">MDICREATESTRUCT</a> structure. <i>lpParam</i> may be <b>NULL</b> if no additional data is needed.
+If an application calls <b>CreateWindow</b> to create a MDI client window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-clientcreatestruct">CLIENTCREATESTRUCT</a> structure. If an MDI client window calls <b>CreateWindow</b> to create an MDI child window, <i>lpParam</i> should point to a <a href="/windows/desktop/api/winuser/ns-winuser-mdicreatestructw">MDICREATESTRUCT</a> structure. <i>lpParam</i> may be <b>NULL</b> if no additional data is needed.
 
 ## -returns
 
@@ -160,7 +160,7 @@ If the function fails, the return value is <b>NULL</b>. To get extended error in
 ## -remarks
 
 Before returning, <b>CreateWindow</b> sends a <a href="/windows/desktop/winmsg/wm-create">WM_CREATE</a> message to the window procedure. For overlapped, pop-up, and child windows, <b>CreateWindow</b> sends <b>WM_CREATE</b>, <a href="/windows/desktop/winmsg/wm-getminmaxinfo">WM_GETMINMAXINFO</a>, and <a href="/windows/desktop/winmsg/wm-nccreate">WM_NCCREATE</a> messages to the window. The
- <i>lParam</i> parameter of the <b>WM_CREATE</b> message contains a pointer to a <a href="/windows/desktop/api/winuser/ns-winuser-createstructa">CREATESTRUCT</a> structure. If the <b>WS_VISIBLE</b> style is specified, <b>CreateWindow</b> sends the window all the messages required to activate and show the window. 
+ <i>lParam</i> parameter of the <b>WM_CREATE</b> message contains a pointer to a <a href="/windows/desktop/api/winuser/ns-winuser-createstructw">CREATESTRUCT</a> structure. If the <b>WS_VISIBLE</b> style is specified, <b>CreateWindow</b> sends the window all the messages required to activate and show the window. 
 
 If the created window is a child window, its default position is at the bottom of the Z-order. If the created window is a top-level window, its default position is at the top of the Z-order (but beneath all topmost windows unless the created window is itself topmost).
 
@@ -262,7 +262,7 @@ For a table of the static control styles you can specify in the <i>dwStyle</i> p
 </table>
 
 
-<b>CreateWindow</b> is implemented as a call to the <a href="/windows/desktop/api/winuser/nf-winuser-createwindowexa">CreateWindowEx</a> function, as shown below.
+<b>CreateWindow</b> is implemented as a call to the <a href="/windows/desktop/api/winuser/nf-winuser-createwindowexw">CreateWindowEx</a> function, as shown below.
 
 
 ``` syntax
@@ -306,7 +306,7 @@ For an example, see <a href="/windows/desktop/winmsg/using-window-classes">Using
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-createwindowexa">CreateWindowEx</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-createwindowexw">CreateWindowEx</a>
 
 
 
@@ -326,11 +326,11 @@ For an example, see <a href="/windows/desktop/winmsg/using-window-classes">Using
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-registerclassa">RegisterClass</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-registerclassw">RegisterClass</a>
 
 
 
-<a href="/windows/desktop/api/winuser/nf-winuser-registerclassexa">RegisterClassEx</a>
+<a href="/windows/desktop/api/winuser/nf-winuser-registerclassexw">RegisterClassEx</a>