Merge pull request #904 from run-ai/itayvallach-patch-3

Itayvallach patch 3

Author: itayvallach

docs/Researcher/user-interface/workspaces/blocks/existing-PVC.md

@@ -1,5 +1,3 @@
-# Persistent volume claim (PVCs)
-
 # Persistent Volumes (PVs) & Persistent Volume Claims (PVCs)
 
 Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) are concepts in Kubernetes for managing storage. A PV is a piece of storage in the cluster, provisioned by an administrator or dynamically by Kubernetes using a StorageClass. It is a resource in the cluster, just like a node is a cluster resource.
@@ -23,8 +21,8 @@ For example: By selecting Department B as the scope of the asset, any user with
 
 There are two different ways of creating data source of type PVC:
 
-1. **Existing PVC**-Data source of type PVC using an existing PVC in the cluster  
-1. **New PVC**-Data source of type PVC by creating a new pvc in the cluster!
+1. **Existing PVC** - Data source of type PVC using an existing PVC in the cluster.
+1. **New PVC** - Data source of type PVC by creating a new PVC in the cluster.
 ![](img/10-pvc.png)
 
 !!! NOTE
@@ -86,5 +84,5 @@ When creating a data source of type PVC using a new PVC, Run:ai creates the PVC
 1. Click Create
 
 !!! NOTES
-    When creating data source of type PVC using a new PVC, the PVC is created immediately in the cluster runai namespace (even if no workload has requested to use this PVC).
-    A PVC created in the cluster by selecting the option “New PVC” never appears as a PVC in the “Existing PVC“ option.
+    When creating data source of type PVC using a new PVC, the PVC is immediately created in the cluster (even if no workload has requested to use this PVC).
+    PVCs created in the cluster using the 'New PVC' option will not appear in the 'Existing PVC' selection.