diff --git a/docs/admin/predeployment_check.md b/docs/admin/predeployment_check.md
index 6c1a7adee76..f2a3ed1d8f5 100644
--- a/docs/admin/predeployment_check.md
+++ b/docs/admin/predeployment_check.md
@@ -166,7 +166,7 @@ If telemetry is enabled in the server configuration file, the telemetry port (91
 must also be accessible on the DAOS server nodes.
 
 Depending of the provider that is used, ech engine might also listens on a range of ports. This is
-the case for the tcp provider. This range will start at the fabric_iface_port specificed in the
+the case for the tcp provider. This range will start at the fabric_iface_port specified in the
 server yaml file and use 2 ports for management, 1 port per target and helper xstream. For instance,
 with fabric_iface_port set to 20000, 16 targets and 4 helper streams, the engine will listen on port
 range from 20000 to 20021 for a total of 22 ports.
diff --git a/src/cart/crt_init.c b/src/cart/crt_init.c
index 429a00e6904..9bf03e91749 100644
--- a/src/cart/crt_init.c
+++ b/src/cart/crt_init.c
@@ -527,8 +527,8 @@ prov_settings_apply(bool primary, crt_provider_t prov, crt_init_options_t *opt)
 	 * Force specific port range for application when using tcp provider to know what
 	 * ports to open when firewall is used.
 	 */
-	if (!crt_is_service() && (prov == CRT_PROV_OFI_TCP || prov = CRT_PROV_OFI_TCP_RXM)) {
-		uint32_t port_low_range = UINT32_MAX;
+	if (!crt_is_service() && (prov == CRT_PROV_OFI_TCP || prov == CRT_PROV_OFI_TCP_RXM)) {
+		uint32_t port_low_range  = UINT32_MAX;
 		uint32_t port_high_range = UINT32_MAX;
 
 		crt_env_get(FI_TCP_PORT_LOW_RANGE, &port_low_range);