Merge pull request #102856 from NavtejSaini-MSFT/patch-42

Fixes https://github.com/MicrosoftDocs/azure-docs/issues/47173

Author: PRMerger7

articles/sql-database/sql-database-managed-instance.md

@@ -297,7 +297,7 @@ The following diagram outlines surface area compatibility in managed instance:
 
 ### Key differences between SQL Server on-premises and in a managed instance
 
-The managed instance deployment option benefits from being always-up-to-date in the cloud, which means that some features in on-premises SQL Server may be either obsolete, retired, or have alternatives. There are specific cases when tools need to recognize that a particular feature works in a slightly different way or that service is not running in an environment you do not fully control:
+The managed instance deployment option benefits from being always-up-to-date in the cloud, which means that some features in on-premises SQL Server may be either obsolete, retired, or have alternatives. There are specific cases when tools need to recognize that a particular feature works in a slightly different way or that the service is running in an environment you do not fully control:
 
 - High-availability is built in and pre-configured using technology similar to [Always On Availability Groups](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server).
 - Automated backups and point in time restore. Customer can initiate `copy-only` backups that do not interfere with automatic backup chain.