From a7a4f9d4cbc1e1b2e11411cfe10a29bc10dffd9b Mon Sep 17 00:00:00 2001
From: CRC <6834943+christophercarney@users.noreply.github.com>
Date: Tue, 5 Nov 2019 00:00:38 -0500
Subject: [PATCH] Improve readability in persistent volume introduction
 (#17176)

* Fix typo in persistent volume intro

* Adjust wording of compute jargon
---
 content/en/docs/concepts/storage/persistent-volumes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index 741fc1f56f..49f2dcfb39 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -25,7 +25,7 @@ This document describes the current state of `PersistentVolumes` in Kubernetes.
 
 ## Introduction
 
-Managing storage is a distinct problem from managing compute. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this, we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.
+Managing storage is a distinct problem from managing compute instances. The `PersistentVolume` subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed. To do this, we introduce two new API resources:  `PersistentVolume` and `PersistentVolumeClaim`.
 
 A `PersistentVolume` (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using [Storage Classes](/docs/concepts/storage/storage-classes/). It is a resource in the cluster just like a node is a cluster resource. PVs are volume plugins like Volumes, but have a lifecycle independent of any individual Pod that uses the PV. This API object captures the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.