Update using-and-managing-discovery.md

Minor change to seed list

Author: danielledennis

articles/external-attack-surface-management/using-and-managing-discovery.md

@@ -62,7 +62,7 @@ Custom discoveries are organized into Discovery Groups. They are independent see
 
     ![Screenshot of pre-baked attack surface selection page.](media/Discovery_7.png)
 
-    Alternatively, users can manually input their seeds. Defender EASM accepts domains, IP blocks, hosts, email contacts, ASNs, certificate common names, and WhoIs organizations as seed values. You can also specify entities to exclude from asset discovery to ensure they are not added to your inventory if detected. For example, this is useful for organizations that have subsidiaries that will likely be connected to their central infrastructure, but do not belong to your organization.
+    Alternatively, users can manually input their seeds. Defender EASM accepts organization names, domains, IP blocks, hosts, email contacts, ASNs, and WhoIs organizations as seed values. You can also specify entities to exclude from asset discovery to ensure they are not added to your inventory if detected. For example, this is useful for organizations that have subsidiaries that will likely be connected to their central infrastructure, but do not belong to your organization.
 
     Once your seeds have been selected, select **Review + Create**.
 
@@ -106,4 +106,4 @@ Similarly, you can click the “Exclusions” tab to see a list of entities that
 
 - [Discovering your attack surface](discovering-your-attack-surface.md)
 - [Understanding asset details](understanding-asset-details.md)
-- [Understanding dashboards](understanding-dashboards.md)
+- [Understanding dashboards](understanding-dashboards.md)