a few more

mikeblome · mikeblome · commit f3cc3d7d5579 · 2018-08-29T13:09:38.000-07:00
diff --git a/docs/atl/reference/atl-text-encoding-functions.md b/docs/atl/reference/atl-text-encoding-functions.md
@@ -422,7 +422,7 @@ inline BOOL QPDecode(
  Pointer to a variable that contains the length in bytes of *szDest*. If the function succeeds, the variable receives the number of bytes written to the buffer. If the function fails, the variable receives the required length in bytes of the buffer.  
   
  [in] *dwFlags*  
- Flags describing how the conversion is to be performed. See [ATLSMTP_QPENCODE Flags](https://msdn.microsoft.com/library/6b15a3ab-8e57-49e4-8104-09b26ebb96c4).  
+ ATLSMTP_QPENCODE flags describing how the conversion is to be performed.  
   
 ### Return Value  
  Returns TRUE on success, FALSE on failure.  
diff --git a/docs/atl/reference/object-map-macros.md b/docs/atl/reference/object-map-macros.md
@@ -35,7 +35,7 @@ DECLARE_OBJECT_DESCRIPTION( x )
  [in] The class object's description.  
   
 ### Remarks  
- ATL enters this description into the object map through the [OBJECT_ENTRY](https://msdn.microsoft.com/abd10ee2-54f0-4f94-9ec2-ddf8f4c8c8cd) macro.  
+ ATL enters this description into the object map through the [OBJECT_ENTRY_AUTO](#object_entry_auto) macro.  
   
  DECLARE_OBJECT_DESCRIPTION implements a `GetObjectDescription` function, which you can use to override the [CComCoClass::GetObjectDescription](ccomcoclass-class.md#getobjectdescription) method.  
 
diff --git a/docs/cpp/standard-conversions.md b/docs/cpp/standard-conversions.md
@@ -237,7 +237,7 @@ int main()
  A pointer to a function can be converted to type `void *`, if type `void *` is large enough to hold that pointer.  
   
 ### Pointer to void  
- Pointers to type **void** can be converted to pointers to any other type, but only with an explicit type cast (unlike in C). (See [Expressions with Explicit Type Conversions](https://msdn.microsoft.com/060ad6b4-9592-4f3e-8509-a20ac84a85ae) for more information about type casts.) A pointer to any type can be converted implicitly to a pointer to type **void**.A pointer to an incomplete object of a type can be converted to a pointer to **void** (implicitly) and back (explicitly). The result of such a conversion is equal to the value of the original pointer. An object is considered incomplete if it is declared, but there is insufficient information available to determine its size or base class.  
+ Pointers to type **void** can be converted to pointers to any other type, but only with an explicit type cast (unlike in C). A pointer to any type can be converted implicitly to a pointer to type **void**.A pointer to an incomplete object of a type can be converted to a pointer to **void** (implicitly) and back (explicitly). The result of such a conversion is equal to the value of the original pointer. An object is considered incomplete if it is declared, but there is insufficient information available to determine its size or base class.  
   
  A pointer to any object that is not **const** or **volatile** can be implicitly converted to a pointer of type `void *`.  
   
diff --git a/docs/dotnet/how-to-migrate-to-clr.md b/docs/dotnet/how-to-migrate-to-clr.md
@@ -74,7 +74,7 @@ COMObj2->Method(args);  // C++ equivalent
  After your project compiles and runs in Visual Studio 2010 you should create new project configurations for **/clr** rather than modifying the default configurations. **/clr** is incompatible with some compiler options and creating separate configurations lets you build your project as native or managed. When **/clr** is selected in the property pages dialog box, project settings not compatible with **/clr** are disabled (and disabled options are not automatically restored if **/clr** is subsequently unselected).  
   
 ### Create New Project Configurations  
- You can use **Copy Settings From** option in the [New Project Configuration Dialog Box](https://msdn.microsoft.com/cca616dc-05a6-4fe3-bdc1-40c72a66f2be) to create a project configuration based on your existing project settings. Do this once for the Debug configuration and once for Release configuration. Subsequent changes can then be applied to the **/clr** -specific configurations only, leaving the original project configurations intact.  
+ You can use **Copy Settings From** option in the **New Project Configuration Dialog Box** (**Build** > **Configuration Manager** > **Active Solution Configuration** > **New**) to create a project configuration based on your existing project settings. Do this once for the Debug configuration and once for Release configuration. Subsequent changes can then be applied to the **/clr** -specific configurations only, leaving the original project configurations intact.  
   
  Projects that use custom build rules may require extra attention.  
   
diff --git a/docs/windows/how-to-add-mfc-support-to-resource-script-files.md b/docs/windows/how-to-add-mfc-support-to-resource-script-files.md
@@ -16,7 +16,7 @@ ms.workload: ["cplusplus", "uwp"]
 
 Normally, when you build an MFC application for Windows using the [MFC Application Wizard](../mfc/reference/mfc-application-wizard.md), the wizard generates a basic set of files (including a resource script (.rc) file) that contains the core features of the Microsoft Foundation classes (MFC). However, if you are editing an .rc file for a Windows application that is not based on MFC, the following features specific to the MFC framework are not available:
 
-- MFC code wizards (previously called "[MFC ClassWizard](https://msdn.microsoft.com/98dc2434-ba93-4e0b-b084-1a4bc26cdf1e)")
+- MFC code wizards
 
 - Menu prompt strings
 
