fixes

MicrosoftDocs · Aug 27, 2021 · 35bcc40 · 35bcc40
1 parent 3adfe84
commit 35bcc40
Show file tree

Hide file tree

Showing 7 changed files with 5 additions and 12 deletions.
diff --git a/...dev-tools/media/casting_debugfeatures.png → ...-core/dev-itpro/dev-ref/media/casting.png b/...dev-tools/media/casting_debugfeatures.png → ...-core/dev-itpro/dev-ref/media/casting.png
diff --git a/...ncationsolutionexplorer_debugfeatures.png → ...-itpro/dev-ref/media/stringtruncation.png b/...ncationsolutionexplorer_debugfeatures.png → ...-itpro/dev-ref/media/stringtruncation.png
diff --git a/articles/fin-ops-core/dev-itpro/dev-ref/xpp-data-primitive.md b/articles/fin-ops-core/dev-itpro/dev-ref/xpp-data-primitive.md
@@ -439,7 +439,7 @@ void StringMethod()
 
 String values can be declared in X++ to contain a maximum number of characters. Typically, this is achieved by encoding this information in an extended data type and setting the **String Size** in the **Properties** window. In the following screenshot, **FMCreditCardNum**cannot exceed 20 characters.
 
-![FMCreditCardNum string size.](media/stringtruncationsolutionexplorer_debugfeatures.png)
+![FMCreditCardNum string size.](media/stringtruncation.png)
 
 Run the following code in the debugger by including it in a static **Main** method to observed the behavior.
 

diff --git a/articles/fin-ops-core/dev-itpro/dev-ref/xpp-language-reference.md b/articles/fin-ops-core/dev-itpro/dev-ref/xpp-language-reference.md
@@ -42,7 +42,7 @@ The standard compilation unit is the same as for other .NET language. If any met
 
 If you are upgrading code from previous versions (AX2012 and earlier), note that the CIL helper methods such as `Global::runClassMethodIL` have been removed, because they're no longer relevant.
 
-For more information, see [What is "managed code"?](dotnet/standard/managed-code.md).
+For more information, see [What is "managed code"?](/dotnet/standard/managed-code.md).
 
 ### The Ignore list
 

diff --git a/articles/fin-ops-core/dev-itpro/dev-ref/xpp-variables-data-types.md b/articles/fin-ops-core/dev-itpro/dev-ref/xpp-variables-data-types.md
@@ -282,7 +282,7 @@ When the **validateField** method checks whether a user has entered a value in a
 
 Casting refers to assignments between variables whose declared types are both in the same inheritance chain. A cast is either a down-cast or an up-cast. Consider the following class hierarchy.
 
-![Class hierarchy for Animal and MotorVehicle.](./media/casting_debugfeatures.png)
+![Class hierarchy for Animal and MotorVehicle.](media/casting.png)
 
 The MotorVehicle class isn't related to the Animal class, though both derive from Object. An **up-cast** happens when assigning an expression of a derived type to a base type:
 

diff --git a/articles/fin-ops-core/dev-itpro/dev-tools/linq-provider-c.md b/articles/fin-ops-core/dev-itpro/dev-tools/linq-provider-c.md
@@ -172,11 +172,4 @@ private IEnumerable RichCustomers(bool orderByName)
 
 LINQ queries can be applied for CRUD operations. But the model for updating, deleting, and inserting records isn't useful for the expression of set based operations. We're now working on extensions to add to the LINQ model that will translate into set based operations.
 
-## Additional resources
-
-[Changes in X++ and the X++ compiler](programming-language-support.md)
-
-[Develop and customize home page](developer-home-page.md)
-
-
-[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../../includes/footer-banner.md)]
diff --git a/...les/fin-ops-core/dev-itpro/extensibility/customize-model-elements-extensions.md b/...les/fin-ops-core/dev-itpro/extensibility/customize-model-elements-extensions.md
@@ -199,7 +199,7 @@ In **Solution Explorer**, in the FleetManagement Discounts project, double-click
 This class contains event handler implementations that subscribe to the **Updating** and **Inserting** events of the **FMRentalCharge** table. Microsoft Dynamics AX introduces data events that can occur on tables and other types. You can subscribe to data events of a table, enabling your application to extend business logic without overlayering base X++ code. Later in this tutorial, you'll see how easy it is to subscribe to table events.
 
 > [!NOTE]
-> Notice that this class is an extension class (indicated by the \_Extension suffix). You can author event handlers in any class, this class does not need to be an extension class. Extension classes are needed in order to create extension methods. For more details on extension methods, refer to the "Extension methods" section of the [X++ debugger features](../dev-tools/new-x-debugger-features.md) article.
+> Notice that this class is an extension class (indicated by the \_Extension suffix). You can author event handlers in any class, this class does not need to be an extension class. Extension classes are needed in order to create extension methods. For more details on extension methods, refer to the "Extension methods" section of the [Extension methods](../dev-ref/xpp-classes-methods.md#extension-methods) article.
 
 ### View the plug-in classes