From b6700b5110a9398c3386b2528316abb9ba64552d Mon Sep 17 00:00:00 2001 From: Joshua Boniface Date: Mon, 18 Jun 2018 21:35:45 -0400 Subject: [PATCH] Tweaks --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d437746d..3c7a027f 100644 --- a/README.md +++ b/README.md @@ -46,7 +46,7 @@ In short, PVC does not look to replace large projects like OpenStack, only a par 1. You have a small (3+ node) KVM cluster and want to efficiently manage your VMs via CLI. 2. You need a very scalable solution to manage dozens of KVM hypervisors. -Really, PVC bennefits both the small and large usecases. +Really, PVC benefits both the small and large use-cases. If your requirement is for a simple and easy-to-use tool to automatically manage VMs, PVC will work for you. ## Why shouldn't you use PVC?