Merge pull request #252969 from Karthigasree/27Sep-SQLDiscovery

SQL discovery update

Author: prmerger-automator[bot]

articles/migrate/how-to-discover-sql-existing-project.md

@@ -6,7 +6,7 @@ ms.author: vivikram
 ms.manager: abhemraj
 ms.topic: how-to
 ms.service: azure-migrate
-ms.date: 04/13/2023
+ms.date: 09/27/2023
 ms.custom: engagement-fy23
 ---
 
@@ -56,7 +56,8 @@ This discovery process is agentless that is, nothing is installed on the target
 3. Once the desired credentials are added, select Start Discovery, to begin the scan.
 
 > [!Note]
-> Allow web apps and SQL discovery to run for sometime before creating assessments for Azure App Service or Azure SQL. If the discovery of web apps and SQL Server instances and databases is not allowed to complete, the respective instances are marked as **Unknown** in the assessment report.
+> - Allow web apps and SQL discovery to run for sometime before creating assessments for Azure App Service or Azure SQL. If the discovery of web apps and SQL Server instances and databases is not allowed to complete, the respective instances are marked as **Unknown** in the assessment report.
+> - In a project containing multiple appliances, it's possible the Web app discovery and assessment agent of one appliance ends up discovering a web app running on a server discovered by another appliance. This doesn't impede the discovery or assessment experience of the web app.
 
 ## Next steps