diff --git a/content/docs/csidriver/features/powerstore.md b/content/docs/csidriver/features/powerstore.md
index 23a13f9e..d05d2806 100644
--- a/content/docs/csidriver/features/powerstore.md
+++ b/content/docs/csidriver/features/powerstore.md
@@ -638,17 +638,3 @@ spec:
 ```
 
 >Note: The access mode ReadWriteOnce allows multiple pods to access a single volume within a single worker node and the behavior is consistent across all supported Kubernetes versions.
-
-
-## NVMe/TCP Support
-
-CSI Driver for Dell Powerstore 2.2.0 and above supports NVMe/TCP provisioning. To enable NVMe/TCP provisioning, blockProtocol on secret should be specified as `NVMeTCP`. In case blockProtocol is specified as `auto`, the driver will be able to find the initiators on the host and choose the protocol accordingly. If the host has multiple protocols enabled, then FC gets the highest priority followed by iSCSI and then NVMeTCP. 
-
-Prerequisites
-
-1. The driver requires NVMe management command-line interface (nvme-cli) to use configure, edit, view or start the NVMe client and target. The nvme-cli utility provides a command-line and interactive shell option. The NVMe CLI tool is installed in the host using the below command.
-`sudo apt install nvme-cli`
-
-2. Modules including the nvme, nvme_core, nvme_fabrics, and nvme_tcp are required for using NVMe over Fabrics using TCP. Load the NVMe and NVMe-OF Modules using the below commands.
-```modprobe nvme
-   modprobe nvme-tcp```
diff --git a/content/docs/csidriver/installation/helm/powerstore.md b/content/docs/csidriver/installation/helm/powerstore.md
index 856e5771..868d7c27 100644
--- a/content/docs/csidriver/installation/helm/powerstore.md
+++ b/content/docs/csidriver/installation/helm/powerstore.md
@@ -139,7 +139,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
     - *username*, *password*: defines credentials for connecting to array.
     - *skipCertificateValidation*: defines if we should use insecure connection or not.
     - *isDefault*: defines if we should treat the current array as a default.
-    - *blockProtocol*: defines what SCSI transport protocol we should use (FC, ISCSI, NVMeTCP, None, or auto).
+    - *blockProtocol*: defines what SCSI transport protocol we should use (FC, ISCSI, None, or auto).
     - *nasName*: defines what NAS should be used for NFS volumes.
     
     Add more blocks similar to above for each PowerStore array if necessary. 
diff --git a/content/docs/csidriver/installation/operator/powerstore.md b/content/docs/csidriver/installation/operator/powerstore.md
index 3e6d156b..8fb2f30f 100644
--- a/content/docs/csidriver/installation/operator/powerstore.md
+++ b/content/docs/csidriver/installation/operator/powerstore.md
@@ -30,7 +30,7 @@ Kubernetes Operators make it easy to deploy and manage the entire lifecycle of c
         password: "password"                      # password for connecting to API
         skipCertificateValidation: true           # indicates if client side validation of (management)server's certificate can be skipped
         isDefault: true                           # treat current array as a default (would be used by storage classes without arrayID parameter)
-        blockProtocol: "auto"                     # what SCSI transport protocol use on node side (FC, ISCSI, NVMeTCP, None, or auto)
+        blockProtocol: "auto"                     # what SCSI transport protocol use on node side (FC, ISCSI, None, or auto)
         nasName: "nas-server"                     # what NAS should be used for NFS volumes
    ```
    Change the parameters with relevant values for your PowerStore array.