Update KnownIssues.md

Author: CarolynRountree

KnownIssues.md

@@ -9,7 +9,7 @@ The following list are known issues. The issue may contain a work-around or an a
 
    If you have only non-JRF user server groups targeted to a dynamic cluster, you will see the following message:
 
-    WLSDPLY-12238: Unable to target non-JRF template server groups for domain type CUSTOM to dynamic cluster(s).
+    WLSDPLY-12238: Unable to target non-JRF template server groups for domain type <your domain typedef> to dynamic cluster(s).
 
    You will not see this message if you have a mix of non-JRF and JRF user server groups targeted to the dynamic
    cluster. WDT cannot detect if a user server group is associated to JRF, and therefore, whether the applyJRF will
@@ -21,9 +21,9 @@ The following list are known issues. The issue may contain a work-around or an a
    the following action as a temporary work-around to the described issue.
 
    1. Add a configured managed server to your dynamic cluster and re-run the createDomain or updateDomain tool.
-      The dynamic cluster becomes "mixed" cluster once the managed server is added. When the WDT tool targets the
+      The dynamic cluster becomes a "mixed" cluster once the managed server is added. When the WDT tool targets the
       user server groups to the configured managed server, the resources are automatically targeted to the cluster
-      by WebLogic, which includes the managed server and the dynamic servers.
+      by WebLogic, which includes both the managed server and the dynamic servers.
 
 **ISSUE**:
    The discoverDomain STDOUT contains many SEVERE messages about cd() and ls() when it is run against a 12.2.1 domain.