Edit

Author: ConnorLand

content/en/docs/releasenotes/studio-pro/10/10.24.md

@@ -37,9 +37,9 @@ This is the [LTS](/releasenotes/studio-pro/lts-mts/#lts) version 10 release for
 - We fixed an issue for the Message Definitions editor where custom values for editable fields like 'External Name' disappeared. (Tickets 263144, 263609, 263817, 264535, 264805, 264850)
 - We fixed an issue in consumed OData services in Studio Pro where importing a metadata file with incorrect XML namespaces would show an "Importing..." progress dialog without ever completing the import.
 - We fixed an issue where `Core.getLicenseInformation().products()` did not return a numeric value if the value was larger than `2147483647`.
-- We fixed an issue that prevented the dialog from closing when pressing the Escape key while editing an access rule (ticket 257016).
-- We fixed an issue where source maps for pluggable widgets were not included correctly in the React client bundle when "Optimize bundle" is set to "No". (Ticket 261353)
-- Fixed an issue where widgets with unbounded dynamic imports (e.g. `await import(path);`) would result in a bundling error when using the React client. They are now marked as external which means they will be resolved when the widget is loaded in the browser. (Ticket 261630)
+- We fixed an issue that prevented a dialog from closing when users pressed <kbd>Escape</kbd> while editing an [access rule](/refguide/access-rules/). (Ticket 257016)
+- We fixed an issue where source maps for pluggable widgets were not included correctly in the React client bundle when **Optimize bundle** is set to **No**. (Ticket 261353)
+- We fixed an issue where widgets with unbounded dynamic imports (for example, `await import(path);`) would result in a bundling error when using the React client. They are now marked as external, which means they will be resolved when the widget is loaded in the browser. (Ticket 261630)
 - We fixed a bug where nanoflows would not be exported when re-added to a page after a full deployment cycle. The issue occurred when a nanoflow was removed from a page during hot-reload, followed by a full deployment, and then re-added during another hot-reload.
 
 ## 10.24.11 {#102411}