edit

Author: ConnorLand

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

@@ -29,31 +29,31 @@ The **Module ID** and **checksum** are stored in a new *manifest.json* file insi
 ### Other New Features
 
 - We introduced a modernized **Variables** pane. It now preserves expanded nodes as you step through the debugger, so you no longer lose your place between steps.
-- The modernized Debug Windows can be switched off in **Edit > Preferences > New features** by unchecking **Use the modernized Debug Windows (Requires restart of Studio Pro)**.
-- We improved offline synchronization error handling so that when the server rejects uploaded objects (for example, due to validation rules or security constraints), the synchronization action now throws a `PartialSynchronizationError` (depending on whether the option "Throw error when server rejects objects during synchronization" is enabled). Nanoflow developers can catch this error in a try/catch block to present a message to the user or take corrective action.
+- The modernized Debug Windows can be switched off in **Edit** > **Preferences** > **New features** by unchecking **Use the modernized Debug Windows (Requires restart of Studio Pro)**.
+- We improved offline synchronization error handling so that when the server rejects uploaded objects (for example, due to validation rules or security constraints), the synchronization action now throws a `PartialSynchronizationError` (as long as **Throw error when server rejects objects during synchronization** option is enabled). Nanoflow developers can catch this error in a try/catch block to present a message to the user or take corrective action.
 - Toggling the web fetch tool in Maia preferences now takes effect immediately, without needing to relaunch Studio Pro.
 - We added the ability for the user to see the current Studio Pro version through the Preferences API.
 - We added a `documentAdded` event to the `IProjectChangesApi`, allowing extensions to react when a new document is added to the project.
-- We added the ability to filter the comparison pane by change status (added, modified, deleted, moved). Filters are persisted across sessions, and an indicator is shown when any filter differs from the default.
-- We added sortable columns to the Comparison Pane. You can now click any column header in the Documents and Elements views to sort the list, making it easier to find and group changes.
+- We added the ability to filter the comparison pane by change status (such as added, modified, deleted, or moved). Filters are persisted across sessions, and an indicator is shown when any filter differs from the default.
+- We added sortable columns to the **Comparison** pane. You can now click any column header in the Documents and Elements views to sort the list, making it easier to find and group changes.
 -  We implemented a new function `DATEFORMAT` in OQL. For more details, see [OQL Expression Syntax](/refguide/oql-expression-syntax/#dateformat-function).
 - We implemented two new functions in OQL: `RPAD` and `LPAD`. For more details, see the documentation for [LPAD](/refguide/oql-expression-syntax/#lpad-function) and [RPAD](/refguide/oql-expression-syntax/#rpad-function).
 - You can now use Maia to work with theming and styling in Studio Pro. Maia can modify theme variables, create custom styling, and manage design properties — for example, updating colors, spacing, and typography across your app based on your styling requirements.
 - Maia can now ask you clarifying questions before proceeding. When Maia needs more information, it will present one or more questions directly in the chat — supporting open-ended, single choice, and multiple choice answers — and use your responses to continue with the right approach.
 - We released the Embedded Client in public Beta. You can now embed your Mendix app into any host application by configuring an [Embedded Navigation Profile](/refguide/navigation/#Embedded) and following the instructions in the [Embedding the Client](/refguide/mendix-client/embedding-the-client/) guide.
 - We added a `permissionsChanged` event to the Extension Permissions API, allowing extensions to be notified when permission states change.
 - You can now add custom instructions on either project or module level. Project-level instructions will be added to every Maia conversation, while module-level ones will be added whenever Maia works with documents of a given module.
-- Maia now thinks before responding. You can see what it's considering in real time, and revisit its reasoning at any point during the conversation.
+- Maia now thinks before responding. You can see what it is considering in real time, and revisit its reasoning at any point during the conversation.
 - MCP OAuth authentication now uses a dedicated callback server on a fixed port range (44380–44384), enabling use with MCP servers that require pre-registered redirect URIs.
 - MCP connections now support Mendix Identity (MxId3) authentication. MCP servers hosted on *.mendix.com automatically receive the user's platform access token.
 - You can now disable the web fetch tool in Maia preferences.
 - You can now add custom skills to app (non-protected) modules. These skills are exported together with other contents of the module.
 - You can now enable the beta feature to configure your own inference provider. OpenAI compatible and Bedrock can be configured per project. The model that will work best is Claude Sonnet 4.6. The best experience remains using the Mendix Platform.
 - Maia is now better at fetching and understanding content from web pages by focusing on the main content.
-- A new Skills panel in Maia shows all custom skills that are currently loaded, their status, and which module they belong to (for module-level skills). You can filter the list to show only skills with errors.
+- A new **Skills** panel in Maia shows all custom skills that are currently loaded, their status, and which module they belong to (for module-level skills). You can filter the list to show only skills with errors.
 - Maia now shows which custom skill (or resource within a skill) it is drawing on while working, so you can follow along as it applies your project's conventions.
-- You can now attach Markdown files (.md, .mdx) to your Maia chat messages. Each file can be up to 50 KB, and you can attach as many as you need. The file contents are sent to Maia as context alongside your prompt.
-- Maia Agent session can be saved by navigating Help --> Support Tools --> Capture Maia Agent Session, making it easier to share session details when troubleshooting or reporting issues.
+- You can now attach Markdown files (*.md*, *.mdx*) to your Maia chat messages. Each file can be up to 50 KB, and you can attach as many as you need. The file contents are sent to Maia as context alongside your prompt.
+- Maia Agent session can be saved by navigating **Help** > **Support Tools** > **Capture Maia Agent Session**, making it easier to share session details when troubleshooting or reporting issues.
 - Data Transformers are now generally available. This allows you to transform complex JSON data, including cases that were never supported before.
   - You can use a Data Transformer as a preprocessing step before passing the data into an Import Mapping, or use the transformed JSON directly, for example to send data to another system.
   - Maia support has been added, so Maia can help creating and modifying Data Transformers.