typos

Author: CarlRabeler

articles/azure-sql/managed-instance/frequently-asked-questions-faq.md

@@ -96,7 +96,7 @@ If both hardware generations are not supported in the same region, changing the
 
 **What if there are no enough IP addresses for performing update operation?**
 
-In case there is no enough IP addresses in the subnet where your managed instance is provisioned, you will have to create new subnet and new managed instance inside it. We also suggest that new subnet is created with more IP addresses alocated so future update operations will avoid similar situation (for propper subnet size, check [how to determine size of vnet subnet](vnet-subnet-determine-size.md). After new instance is provisioned, you can manually back up and restore data between the old and new instance or perform cross-instance [point-in-time restore](point-in-time-restore.md?tabs=azure-powershell). 
+In case there is no enough IP addresses in the subnet where your managed instance is provisioned, you will have to create new subnet and new managed instance inside it. We also suggest that new subnet is created with more IP addresses allocated so future update operations will avoid similar situation (for proper subnet size, check [how to determine size of vnet subnet](vnet-subnet-determine-size.md). After new instance is provisioned, you can manually back up and restore data between the old and new instance or perform cross-instance [point-in-time restore](point-in-time-restore.md?tabs=azure-powershell). 
 
 
 ## Tune performance

articles/azure-sql/managed-instance/resource-limits.md

@@ -92,7 +92,7 @@ Find more information about the [resource limits in SQL Managed Instance pools i
 
 ### File IO characteristics in General Purpose tier
 
-In the General Purpose service tier every database file gets dedicated IOPS and throughput that depend on the file size. Bigger data files get mroe IOPS and throughput. IO characteristics of the database files are shown in the following table:
+In the General Purpose service tier every database file gets dedicated IOPS and throughput that depend on the file size. Bigger data files get more IOPS and throughput. IO characteristics of the database files are shown in the following table:
 
 | File size | >=0 and <=128 GiB | >128 and <=256 GiB | >256 and <= 512 GiB | >0.5 and <=1 TiB    | >1 and <=2 TiB    | >2 and <=4 TiB | >4 and <=8 TiB |
 |---------------------|-------|-------|-------|-------|-------|-------|-------|

articles/data-factory/create-azure-ssis-integration-runtime.md

@@ -124,7 +124,7 @@ After your data factory is created, open its overview page in the Azure portal.
 
     1. For **Catalog Database Server Endpoint**, select the endpoint of your SQL Database or SQL Managed Instance. 
 
-       Based on the selected SQL Database or SQL Managed Instance, the SSISDB instance can be created on your behalf as a single database or as part of an elastic pool in SQL Database, or as an instance database in a SQL Managed Instance. It can be accessible in a public network or by joining a virtual network. For guidance in choosing the prouct to host SSISDB, see the [Compare Azure SQL Database and SQL Managed Instance](#comparison-of-sql-database-and-sql-managed-instance).
+       Based on the selected SQL Database or SQL Managed Instance, the SSISDB instance can be created on your behalf as a single database or as part of an elastic pool in SQL Database, or as an instance database in a SQL Managed Instance. It can be accessible in a public network or by joining a virtual network. For guidance in choosing the product to host SSISDB, see the [Compare Azure SQL Database and SQL Managed Instance](#comparison-of-sql-database-and-sql-managed-instance).
        If you select SQL Database with IP firewall rules/virtual network service endpoints or SQL Managed Instance with private endpoint to host SSISDB, or if you require access to on-premises data without configuring a self-hosted IR, you need to join your Azure-SSIS IR to a virtual network. For more information, see [Join an Azure-SSIS IR to a virtual network](https://docs.microsoft.com/azure/data-factory/join-azure-ssis-integration-runtime-virtual-network). 
 
     1. Select the **Use AAD authentication with the managed identity for your ADF** check box to choose the authentication method for your database server to host SSISDB. You'll choose either SQL authentication or Azure AD authentication with the managed identity for your data factory.