small fixes

Tyler Whitney · Tyler Whitney · commit 89c572eec787 · 2020-05-28T18:39:46.000-07:00
diff --git a/docs/mfc/reference/cftpfilefind-class.md b/docs/mfc/reference/cftpfilefind-class.md
@@ -159,7 +159,7 @@ The file and path of the Universal Resource Locator (URL).
 
 ### Remarks
 
-`GetFileURL` is similar to the member function [CFileFind::GetFilePath](../../mfc/reference/cfilefind-class.md#getfilepath), except that in addition to providing the result in URL format, it doesn't include the filename. For example:`ftp://moose/dir`.
+`GetFileURL` is similar to the member function [CFileFind::GetFilePath](../../mfc/reference/cfilefind-class.md#getfilepath) except that it provides the result in URL format. As with `CFileFind::GetFilePath`, the result doesn't include the filename. For example, `file1.txt` located in `//moose/dir/file1.txt:` returns `ftp://moose/dir/`.
 
 ## See also
 
diff --git a/docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md b/docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md
@@ -354,7 +354,7 @@ Next, you'll learn how to create the code for a Windows desktop application in V
 
    One important message to handle is the [WM_PAINT](/windows/win32/gdi/wm-paint) message. The application receives the `WM_PAINT` message when part of its displayed window must be updated. The event can occur when a user moves a window in front of your window, then moves it away again. Your application doesn't know when these events occur. Only Windows knows, so it notifies your app with a `WM_PAINT` message. When the window is first displayed, all of it must be updated.
 
-   To handle a `WM_PAINT` message, first call [BeginPaint](/windows/win32/api/winuser/nf-winuser-beginpaint), then handle all the logic to layout the text, buttons, and other controls in the window, and then call [EndPaint](/windows/win32/api/winuser/nf-winuser-endpaint). For the application, the logic between the beginning call and the ending call displays the string "Hello, Windows desktop!" in the window. In the following code, the [TextOut](/windows/win32/api/wingdi/nf-wingdi-textoutw) function is used to display the string.
+   To handle a `WM_PAINT` message, first call [BeginPaint](/windows/win32/api/winuser/nf-winuser-beginpaint), then handle all the logic to lay out the text, buttons, and other controls in the window, and then call [EndPaint](/windows/win32/api/winuser/nf-winuser-endpaint). For the application, the logic between the beginning call and the ending call displays the string "Hello, Windows desktop!" in the window. In the following code, the [TextOut](/windows/win32/api/wingdi/nf-wingdi-textoutw) function is used to display the string.
 
    ```cpp
    PAINTSTRUCT ps;
@@ -379,8 +379,8 @@ Next, you'll learn how to create the code for a Windows desktop application in V
    }
    ```
 
-   `HDC` in the code is a handle to a device context, which is a data structure used to communicate with the graphics subsystem about the window. Calling `BeginPaint` and `EndPaint` tells the graphics subsystem that you are updating the invalidated region and that no more painting is required until it is invalidated again. Otherwise, you will keep getting WM_PAINT messages for that region.
-
+   `HDC` in the code is a handle to a device context, which is used to draw in the window's client area. Use the `BeginPaint` and `EndPaint` functions to prepare for and complete the drawing in the client area. `BeginPaint` returns a handle to the display device context used for drawing in the client area; `EndPaint` ends the paint request and releases the device context.
+   
 1. An application typically handles many other messages. For example, [WM_CREATE](/windows/win32/winmsg/wm-create) when a window is first created, and [WM_DESTROY](/windows/win32/winmsg/wm-destroy) when the window is closed. The following code shows a basic but complete `WndProc` function.
 
    ```cpp
