Reorder fixes

Author: ConnorLand

content/en/docs/releasenotes/studio-pro/11/11.6.md

@@ -21,19 +21,19 @@ mts: true
 - We improved the `Set all to` toggle in the entity access rules editor so that when some members have access rights and others don't, the toggle now disables all rights instead of enabling them. This prevents the `Write` toggle from unexpectedly affecting read access.
 
 ### Fixes
-    
+
+- We fixed an issue where an Oops pop-up window appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502)    
 - We fixed an issue in offline apps that could result in errors like "[Synchronization] SQLiteError: table mx10414574138294561$_guidToTable has no column named inaccessibleAttrs" by ensuring database migrations happen properly for all users in the client database. (Tickets 264910, 265393, 269740)
-- We fixed an issue where SVGs failed to render in the offline profile.
-- We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502)
-- We fixed an issue where an Oops dialog appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420)
-- We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Tickets 270889, 271134)
-- We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865)
-- We fixed an issue that when document was modified on one source and deleted on other during combination process user had no option to resolve a conflict by deleting a document.
-- We fixed an issue when after performing rebase or cherry-pick when user didn’t close the push notification bar and started with new combination operation could end up with two visible notification bars
+- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403)
 - In the logic editors, we fixed an issue when Show Message activity could have an empty caption after initial loading of the microflow. (Ticket 268024).
 - In the logic editors, we fixed an issue when Extracting submicroflow the sequence flow in the original microflow had invalid condition value, and extracted microflow was missing one. (Ticket 269233).
-- We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403)
 - We fixed an issue where a long-running after startup microflow causes the node to be assumed crashed by other nodes. (Ticket 269993)
+- We fixed an issue where an Oops pop-up window appeared with conditional editability settings when a widget referenced a default variable. (Ticket 270420)
+- We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865)
+- We fixed an issue where, when downloading a widget from the Marketplace or updating a widget via the widget updater, the widget MPK file would become corrupted. This corruption led to an error dialog appearing in Studio Pro when attempting to read the widget package. (Tickets 270889, 271134)
+- We fixed an issue where SVGs failed to render in the offline profile.
+- We fixed an issue that when document was modified on one source and deleted on other during combination process user had no option to resolve a conflict by deleting a document.
+- We fixed an issue when after performing rebase or cherry-pick when user did not close the push notification bar and started with new combination operation could end up with two visible notification bars
 - We fixed an issue in the React client where enabling autofocus on a popup that only contained focusable elements in the header or footer resulted in no element being focused.
 
 ## 11.6.3 {#1163}