Corrected maven co-ordinates and minor wording

Author: RamaKrishna-4

rosettanet/3.0/modules/ROOT/pages/rosettanet-connector-upgrade-migrate.adoc

@@ -54,7 +54,7 @@ For FIPS modes, the Mule runtime and BCFIPS requirements apply.
 [%header%autowidth]
 |===
 |Security Mode | Global Configuration | Default Name | Required Library Maven Coordinates
-|non-FIPS | `RosettaNet External Libs - Non FIPS` | `RosettaNet__External_Libs___Non_FIPS` | org.bouncycastle:bcpkix-jdk18on:1.82, org.bouncycastle:bcprov-jdk18on:1.82, org.bouncycastle:bcjmail-jdk18on:1.82, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2
+|non-FIPS | `RosettaNet External Libs - Non FIPS` | `RosettaNet__External_Libs___Non_FIPS` | org.bouncycastle:bcpkix-jdk18on:1.84, org.bouncycastle:bcprov-jdk18on:1.84, org.bouncycastle:bcjmail-jdk18on:1.84, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2
 |FIPS 140-2 | `RosettaNet External Libs - FIPS 140-2` | `RosettaNet__External_Libs___FIPS_140_2` | org.bouncycastle:bcjmail-fips:1.0.4, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2
 |FIPS 140-3 | `RosettaNet External Libs - FIPS 140-3` | `RosettaNet__External_Libs___FIPS_140_3` | org.bouncycastle:bcjmail-fips:2.1.6, com.sun.activation:jakarta.activation:2.0.1, com.sun.mail:jakarta.mail:2.0.2
 |===
@@ -465,7 +465,7 @@ Add `-Dmule.security.model=fips140-2` if you're using `RosettaNet Connector Exte
 Add `-Dmule.security.model=fips140-3` if you're using `RosettaNet Connector External Libs - FIPS 140-3`.
 * *External Libs - ... configuration selected, but '...' is not on the classpath*
 + 
-Add the correct implementation dependency for your selected security mode or make sure the external library configuration imports the dependency. If you receive a warning, make sure only the library for your active security mode remains on the `classpath` by removing any additional RosettaNet cryptographic implementations.
+Add the correct implementation dependency for your selected security mode or make sure the external library configuration imports the dependency. If you receive a warning, make sure only the external library configuration for your active security mode only remain by removing any additional external library configurations.
 * *Startup or Crypto Errors in FIPS Mode*
 + 
 Make sure `mule.security.model` matches your runtime FIPS setup and that BCFIPS is installed and registered. Set `org.bouncycastle.fips.approved_only` to `true` if required.