updating

Author: billmath

articles/active-directory/hybrid/connect/reference-connect-version-history.md

@@ -70,18 +70,18 @@ For version history information on retired versions, see [Azure AD Connect: Vers
 > [!NOTE]
 > Releasing a new version of Azure AD Connect requires several quality-control steps to ensure the operation functionality of the service. While we go through this process, the version number of a new release and the release status are updated to reflect the most recent state.
 
-Not all releases of Azure AD Connect are made available for auto-upgrade. The release status indicates whether a release is made available for auto-upgrade or for download only. If auto-upgrade was enabled on your Azure AD Connect server, that server automatically upgrades to the latest version of Azure AD Connect that's released for auto-upgrade. Not all Azure AD Connect configurations are eligible for auto-upgrade.
+Not all releases of Azure AD Connect are made available for autoupgrade. The release status indicates whether a release is made available for autoupgrade or for download only. If autoupgrade was enabled on your Azure AD Connect server, that server automatically upgrades to the latest version of Azure AD Connect that's released for autoupgrade. Not all Azure AD Connect configurations are eligible for autoupgrade.
 
-Auto-upgrade is meant to push all important updates and critical fixes to you. It isn't necessarily the latest version because not all versions will require or include a fix to a critical security issue. (This example is just one of many.) Critical issues are usually addressed with a new version provided via auto-upgrade. If there are no such issues, there are no updates pushed out by using auto-upgrade. In general, if you're using the latest auto-upgrade version, you should be good.
+Auto-upgrade is meant to push all important updates and critical fixes to you. It isn't necessarily the latest version because not all versions will require or include a fix to a critical security issue. (This example is just one of many.) Critical issues are usually addressed with a new version provided via autoupgrade. If there are no such issues, there are no updates pushed out by using autoupgrade. In general, if you're using the latest autoupgrade version, you should be good.
 
 If you want all the latest features and updates, check this page and install what you need.
 
-To read more about auto-upgrade, see [Azure AD Connect: Automatic upgrade](how-to-connect-install-automatic-upgrade.md).
+To read more about autoupgrade, see [Azure AD Connect: Automatic upgrade](how-to-connect-install-automatic-upgrade.md).
 
 ## 2.2.1.0
 
 ### Release status
-5/23/2023: Released for auto-upgrade only
+5/23/2023: Released for autoupgrade only
 
 ### Functional Changes
  - We have enabled Auto Upgrade for tenants with custom synchronization rules. Note that deleted (not disabled) default rules will be re-created and enabled upon Auto Upgrade.
@@ -130,15 +130,15 @@ To read more about auto-upgrade, see [Azure AD Connect: Automatic upgrade](how-t
 ## 2.1.16.0
 
 ### Release status
-8/2/2022: Released for download and auto-upgrade.
+8/2/2022: Released for download and autoupgrade.
 
 ### Bug fixes
- - We fixed a bug where auto-upgrade fails when the service account is in "UPN" format.
+ - We fixed a bug where autoupgrade fails when the service account is in "UPN" format.
 
 ## 2.1.15.0
 
 ### Release status
-7/6/2022: Released for download, will be made available for auto-upgrade soon.
+7/6/2022: Released for download, will be made available for autoupgrade soon.
 
 > [!IMPORTANT] 
 > We have discovered a security vulnerability in the Azure AD Connect Admin Agent. If you have installed the Admin Agent previously it is important that you update your Azure AD Connect server(s) to this version to mitigate the vulnerability.
@@ -207,7 +207,7 @@ To read more about auto-upgrade, see [Azure AD Connect: Automatic upgrade](how-t
 
 ### Release status
 
-12/15/2021: Released for download only, not available for auto-upgrade
+12/15/2021: Released for download only, not available for autoupgrade
 
 ### Bug fixes
 
@@ -239,11 +239,11 @@ To read more about auto-upgrade, see [Azure AD Connect: Automatic upgrade](how-t
 
 ### Release status
 
-10/13/2021: Released for download and auto-upgrade
+10/13/2021: Released for download and autoupgrade
 
 ### Bug fixes
 
-- We fixed a bug where the auto-upgrade process attempted to upgrade Azure AD Connect servers that are running older Windows OS version 2008 or 2008 R2 and failed. These versions of Windows Server are no longer supported. In this release, we only attempt auto-upgrade on machines that run Windows Server 2012 or newer.
+- We fixed a bug where the autoupgrade process attempted to upgrade Azure AD Connect servers that are running older Windows OS version 2008 or 2008 R2 and failed. These versions of Windows Server are no longer supported. In this release, we only attempt autoupgrade on machines that run Windows Server 2012 or newer.
 - We fixed an issue where, under certain conditions, miisserver failed because of an access violation exception.
 
 ### Known issues
@@ -257,7 +257,7 @@ When you upgrade to this V1.6 build or any newer builds, the group membership li
 
 ### Release status
 
-9/30/2021: Released for download only, not available for auto-upgrade
+9/30/2021: Released for download only, not available for autoupgrade
 
 ### Bug fixes
 
@@ -282,7 +282,7 @@ When you upgrade to this V1.6 build or any newer builds, the group membership li
 
 ### Release status
 
-9/21/2021: Released for download and auto-upgrade
+9/21/2021: Released for download and autoupgrade
 
 ### Functional changes
 
@@ -301,15 +301,15 @@ When you upgrade to this V1.6 build or any newer builds, the group membership li
 
 ### Release status
 
-9/14/2021: Released for download only, not available for auto-upgrade
+9/14/2021: Released for download only, not available for autoupgrade
 
 ### Bug fixes
 
 - We fixed a security issue where an unquoted path was used to point to the Azure AD Connect service. This path is now a quoted path.
 - We fixed an import configuration issue with writeback enabled when you use the existing Azure AD Connector account.
 - We fixed an issue in Set-ADSyncExchangeHybridPermissions and other related cmdlets, which were broken from V1.6 because of an invalid inheritance type.
 - We fixed an issue with the cmdlet we published in a previous release to set the TLS version. The cmdlet overwrote the keys, which destroyed any values that were in them. Now a new key is created only if one doesn't already exist. We added a warning to let users know the TLS registry changes aren't exclusive to Azure AD Connect and might affect other applications on the same server.
-- We added a check to enforce auto-upgrade for V2.0 to require Windows Server 2016 or newer.
+- We added a check to enforce autoupgrade for V2.0 to require Windows Server 2016 or newer.
 - We added the Replicating Directory Changes permission in the Set-ADSyncBasicReadPermissions cmdlet.
 - We made a change to prevent UseExistingDatabase and import configuration from being used together because they could contain conflicting configuration settings.
 - We made a change to allow a user with the Application Admin role to change the App Proxy service configuration.
@@ -326,14 +326,14 @@ When you upgrade to this V1.6 build or any newer builds, the group membership li
 
 ### Release status
 
-8/19/2021: Released for download only, not available for auto-upgrade
+8/19/2021: Released for download only, not available for autoupgrade
 
 > [!NOTE]
 > This is a hotfix update release of Azure AD Connect. This release requires Windows Server 2016 or newer. This hotfix addresses an issue that's present in version 2.0 and in Azure AD Connect version 1.6. If you're running Azure AD Connect on an older Windows server, install the [1.6.13.0](#16130) build instead.
 
 ### Release status
 
-8/19/2021: Released for download only, not available for auto-upgrade
+8/19/2021: Released for download only, not available for autoupgrade
 
 ### Known issues
 
@@ -348,7 +348,7 @@ We fixed a bug that occurred when a domain was renamed and Password Hash Sync fa
 > [!NOTE]
 > This release is a hotfix update release of Azure AD Connect. It's intended to be used by customers who are running Azure AD Connect on a server with Windows Server 2012 or 2012 R2.
 
-8/19/2021: Released for download only, not available for auto-upgrade
+8/19/2021: Released for download only, not available for autoupgrade
 
 ### Bug fixes
 
@@ -362,7 +362,7 @@ There are no functional changes in this release.
 
 ### Release status
 
-8/17/2021: Released for download only, not available for auto-upgrade
+8/17/2021: Released for download only, not available for autoupgrade
 
 ### Bug fixes
 
@@ -382,7 +382,7 @@ To download the latest version of Azure AD Connect 2.0, see the [Microsoft Downl
 
 ### Release status
 
-8/10/2021: Released for download only, not available for auto-upgrade
+8/10/2021: Released for download only, not available for autoupgrade
 
 ### Functional changes
 
@@ -397,7 +397,7 @@ This release addresses a vulnerability as documented in [this CVE](https://msrc.
 
 ### Release status
 
-8/10/2021: Released for download only, not available for auto-upgrade
+8/10/2021: Released for download only, not available for autoupgrade
 
 ### Functional changes
 
@@ -410,7 +410,7 @@ There are no functional changes in this release.
 
 ### Release status
 
-7/20/2021: Released for download only, not available for auto-upgrade
+7/20/2021: Released for download only, not available for autoupgrade
 
 ### Functional changes
 
@@ -509,7 +509,7 @@ You can use these cmdlets to retrieve the TLS 1.2 enablement status or set it as
 
 ### Release status
 
-3/31/2021: Released for download only, not available for auto-upgrade
+3/31/2021: Released for download only, not available for autoupgrade
 
 ### Bug fixes
 
@@ -527,7 +527,7 @@ This release fixes a bug that occurred in version 1.6.2.4. After upgrade to that
 
 ### Release status
 
-3/19/2021: Released for download, not available for auto-upgrade
+3/19/2021: Released for download, not available for autoupgrade
 
 ### Functional changes