diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index fe26b85..5a5b85f 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,8 +6,8 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
-      <item value="Specifies the [SystemUiMode] to have visible when the application is running. The `overlays` argument is a list of [SystemUiOverlay] enum values denoting the overlays to show when configured with [SystemUiMode.manual]. If a particular mode is unsupported on the platform, enabling or disabling that mode will be ignored. The settings here can be overridden by the platform when System UI becomes necessary for functionality. For example, on Android, when the keyboard becomes visible, it will enable the navigation bar and status bar system UI overlays. When the keyboard is closed, Android will not restore the previous UI visibility settings, and the UI visibility cannot be changed until 1 second after the keyboard is closed to prevent malware locking users from navigation buttons. To regain &quot;fullscreen&quot; after text entry, the UI overlays can be set again after a delay of at least 1 second through [restoreSystemUIOverlays] or calling this again. Otherwise, the original UI overlay settings will be automatically restored only when the application loses and regains focus. Alternatively, a [SystemUiChangeCallback] can be provided to respond to changes in the System UI. This will be called, for example, when in [SystemUiMode.leanBack] and the user taps the screen to bring up the system overlays. The callback provides a boolean to represent if the application is currently in a fullscreen mode or not, so that the application can respond to these changes. When `systemOverlaysAreVisible` is true, the application is not fullscreen. See [SystemChrome.setSystemUIChangeCallback] to respond to these changes in a fullscreen application." />
       <item value="Fullscreen display with status and navigation elements rendered over the application. Available starting at SDK 29 or Android 10. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be visible. The system overlays will not disappear or reappear in this mode as they are permanently displayed on top of the application. See also: [SystemUiOverlayStyle], can be used to configure transparent status and navigation bars with or without a contrast scrim." />
+      <item value="Specifies the [SystemUiMode] to have visible when the application is running. The `overlays` argument is a list of [SystemUiOverlay] enum values denoting the overlays to show when configured with [SystemUiMode.manual]. If a particular mode is unsupported on the platform, enabling or disabling that mode will be ignored. The settings here can be overridden by the platform when System UI becomes necessary for functionality. For example, on Android, when the keyboard becomes visible, it will enable the navigation bar and status bar system UI overlays. When the keyboard is closed, Android will not restore the previous UI visibility settings, and the UI visibility cannot be changed until 1 second after the keyboard is closed to prevent malware locking users from navigation buttons. To regain &quot;fullscreen&quot; after text entry, the UI overlays can be set again after a delay of at least 1 second through [restoreSystemUIOverlays] or calling this again. Otherwise, the original UI overlay settings will be automatically restored only when the application loses and regains focus. Alternatively, a [SystemUiChangeCallback] can be provided to respond to changes in the System UI. This will be called, for example, when in [SystemUiMode.leanBack] and the user taps the screen to bring up the system overlays. The callback provides a boolean to represent if the application is currently in a fullscreen mode or not, so that the application can respond to these changes. When `systemOverlaysAreVisible` is true, the application is not fullscreen. See [SystemChrome.setSystemUIChangeCallback] to respond to these changes in a fullscreen application." />
       <item value="Declares manually configured [SystemUiOverlay]s. When using this mode with [SystemChrome.setEnabledSystemUIMode], the preferred overlays must be set by the developer. When [SystemUiOverlay.top] is enabled, the status bar will remain visible on all platforms. Omitting this overlay will hide the status bar on iOS &amp; Android. When [SystemUiOverlay.bottom] is enabled, the navigation bar and home indicator of Android and iOS applications will remain visible. Omitting this overlay will hide them. Omitting both overlays will result in the same configuration as [SystemUiMode.leanBack]." />
       <item value="Fullscreen display with status and navigation bars presentable through a swipe gesture at the edges of the display. Available starting at SDK 19 or Android K. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be hidden for a similar fullscreen experience. A swipe gesture from the edge of the screen displays overlays. In contrast to [SystemUiMode.immersiveSticky], this gesture is not received by the application. See also: [SystemUiChangeCallback], used to listen and respond to the change in system overlays." />
       <item value="Fullscreen display with status and navigation bars presentable by tapping anywhere on the display. Available starting at SDK 16 or Android J. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be hidden for a similar fullscreen experience. Tapping on the screen displays overlays, this gesture is not received by the application. See also: [SystemUiChangeCallback], used to listen and respond to the change in system overlays." />
@@ -59,8 +59,8 @@
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="450" />
-        <entry key="ENGLISH" value="451" />
+        <entry key="CHINESE" value="451" />
+        <entry key="ENGLISH" value="452" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>