Apply suggestion from @Cristian-Venticinque

Co-authored-by: Cristian-Venticinque <46459586+Cristian-Venticinque@users.noreply.github.com>

Author: Crispy-Salesforce

modules/ROOT/pages/int-versions.adoc

@@ -75,7 +75,7 @@ When you run or debug an application, the IDE checks if the exact Mule runtime v
 * Open *Project Properties* to select or download the required Mule runtime version
 
 [NOTE]
-Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule runtime. Newer Mule runtime versions turn on feature flags by default. See xref:mule-runtime::feature-flagging.adoc[]. This can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change.
+Changing the minimum Mule version (`minMuleVersion`) manually can have serious implications. This requires a full test of your application so it works correctly with the target Mule version. Newer Mule runtime versions turn on feature flags by default. See xref:mule-runtime::feature-flagging.adoc[]. This can change behavior that was fixed in later versions. Your application can rely on behavior that was later corrected or on a previous issue. Prefer changing the Mule version through *Project Properties*, and always run full regression tests after any version change.
 
 When a Mule or Java version isn't set for a project, the IDE's canvas and notifications provide a *Set version* button that opens the *Project Properties* tab. You can also navigate directly to the *Project Properties* tab.