Update 2998527-incorrect-time-timezoneinfo.md

Edit review per CI 6382

Author: przlplx

support/developer/dotnet/framework/general/2998527-incorrect-time-timezoneinfo.md

@@ -1,23 +1,23 @@
 ---
-title: KB2998527 causes wrong code lookups on past dates
-description: This article explains the problem where update 2998527 causes incorrect code lookups on past dates when the application use TimeZoneInfo.
+title: KB2998527 Causes Wrong Code Lookups on Past Dates
+description: This article explains how update 2998527 causes incorrect code lookups on past dates when an application uses TimeZoneInfo.
 ms.date: 07/08/2025
 ms.reviewer: leecow
 ms.custom: sap:Class Library Namespaces
 ms.topic: troubleshooting-problem-resolution
-#customer intent: As a developer, I want to fix incorrect code lookups on past dates when using the TimeZoneInfo class so my application handles time zones correctly.
+#customer intent: As a developer, I want to fix incorrect code lookups on past dates when I use the TimeZoneInfo class so that my application handles time zones correctly.
 ---
 # Update 2998527 causes incorrect code lookups on past dates
 
-This article explains the problem where [KB 2998527](https://support.microsoft.com/help/2998527) causes incorrect code lookups on past dates when you use the `TimeZoneInfo` class in an application.
+This article explains a problem in [Microsoft Knowledge Base article 2998527](https://support.microsoft.com/help/2998527) that causes incorrect code lookups on past dates when you use the `TimeZoneInfo` class in an application.
 
 _Applies to:_ .NET Framework 4.6, 4.5
 
 _Original KB number:_ 3012229
 
 ## Symptoms
 
-After October 26, 2014, applications that are hosted on systems that have the September 2014 Russian time zone update ([KB 2998527](https://support.microsoft.com/help/2998527)) installed and that use the Microsoft .NET Framework might calculate time incorrectly when they use the `TimeZoneInfo` class.
+After October 26, 2014, applications that are hosted on systems that have the September 2014 Russian time zone update ([KB 2998527](https://support.microsoft.com/help/2998527)) installed and that use Microsoft .NET Framework might calculate time incorrectly when they use the `TimeZoneInfo` class.
 
 This problem occurs in the following time zones:
 
@@ -44,19 +44,19 @@ DateTime dt = TimeZoneInfo.ConvertTimeFromUtc(new DateTime(2013, 6, 1), tz);
 Console.WriteLine(dt);
 ```
 
-Before you apply KB 2998527, this code correctly returns the date and time as June 1, 2013 at 04:00. After you apply update, the code incorrectly returns the date and time as June 1, 2013 at 03:00.
+Before you apply KB 2998527, this code correctly returns the date and time as June 1, 2013 at 04:00. After you apply the update, the code returns the date and time incorrectly as June 1, 2013 at 03:00.
 
 ## Cause
 
-This problem occurs because a change in the base offset of a time zone breaks any code in the affected time zones if that code looks up past dates by using `TimeZoneInfo` in the .NET Framework. This is because the .NET Framework can't track year-to-year changes in the base offset.
+This problem occurs because a change in the base offset of a time zone breaks any code in the affected time zones if that code looks up past dates by using `TimeZoneInfo` in .NET Framework. This problem occurs because .NET Framework can't track year-to-year changes in the base offset.
 
-This problem was exposed by the changes to Russian time zones that are described in Microsoft Knowledge Base article 2998527.
+This problem was exposed by the changes to Russian time zones that are described in KB 2998527.
 
-The .NET Framework previously ignored the UTC offset that is set in an internal adjustment rule. Instead, it used the base UTC offset in certain calculations. The .NET Framework also ignored adjustment rules that don't have daylight transitions.
+Previously, .NET Framework ignored the UTC offset that's set in an internal adjustment rule. Instead, it used the base UTC offset in certain calculations. .NET Framework also ignored adjustment rules that don't have daylight transitions.
 
 ## Solution
 
-If your .NET application uses `TimeZoneInfo`, update it with the latest Windows time zone information. If applicable, you should also ensure that your application properly handles the latest time zone rules for Russia.
+If your .NET application uses `TimeZoneInfo`, update it to use the latest Windows time zone information. If applicable, you should also make sure that your application correctly handles the latest time zone rules for Russia.
 
 ## Related content