From 2521dbb54a09f502abe2bdb46dd5e87d63e008a0 Mon Sep 17 00:00:00 2001 From: Dani Halfin Date: Tue, 3 Sep 2019 16:40:40 -0700 Subject: [PATCH] removing even more more spaces --- ...abling-compatibility-fixes-in-compatibility-administrator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md b/windows/deployment/planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md index 487a1a93d2..565b9b6833 100644 --- a/windows/deployment/planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md +++ b/windows/deployment/planning/enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md @@ -32,7 +32,7 @@ You can disable and enable individual compatibility fixes in your customized dat Customized compatibility databases can become quite complex as you add your fixes for the multiple applications found in your organization. Over time, you may find you need to disable a particular fix in your customized database. For example, if a software vendor releases a fix for an issue addressed in one of your compatibility fixes, you must validate that the vendor's fix is correct and that it resolves your issue. To do this, you must temporarily disable the compatibility fix and then test your application. ->[!IMPORTANT]   +>[!IMPORTANT] >Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to work with custom databases for 32-bit applications and the 64-bit version to work with custom databases for 64-bit applications.