Merge pull request #97899 from guyhay/guy's-small-updates

Updated code segment

Author: PRMerger9

articles/data-lake-analytics/dotnet-upgrade-troubleshoot.md

@@ -34,7 +34,7 @@ Check for the potential of backwards-compatibility breaking issues by running th
 1. Run the backwards-compatibility checker on your .NET DLLs either by
    1. Using the Visual Studio Extension at [.NET Portability Analyzer Visual Studio Extension](https://marketplace.visualstudio.com/items?itemName=ConnieYau.NETPortabilityAnalyzer)
    1. Downloading and using the standalone tool from [GitHub dotnetapiport](https://github.com/microsoft/dotnet-apiport). Instructions for running standalone tool are at [GitHub dotnetapiport breaking changes](https://github.com/microsoft/dotnet-apiport/blob/dev/docs/HowTo/BreakingChanges.md)
-   1. For 4.7.2. compatibility read isRetargeting == True are the breaking changes.
+   1. For 4.7.2. compatibility, `read isRetargeting == True` identifies possible issues.
 2. If the tool indicates if your code may be impacted by any of the possible backwards-incompatibilities (some common examples of incompatibilities are listed below),  you can further check by
    1. Analyzing your code and identifying if your code is passing values to the impacted APIs
    1. Perform a runtime check. The runtime deployment isn't done side-by-side in ADLA. You can perform a runtime check before the upgrade, using VisualStudio’s local run with a local .NET Framework 4.7.2 against a representative data set.