Update wording on Reserved Hardware

Signed-off-by: Chris Privitere <23177737+cprivitere@users.noreply.github.com>

README.md

@@ -44,7 +44,7 @@ If you do not change the generated `yaml` files, it will use defaults. You can l
 
 ### Reserved Hardware
 
-If you'd like to use reserved instances for your cluster. You need to edit your cluster yaml and add a hardwareReservationID field to your PacketMachineTemplates. That field can container either a comma separated list of hardware reservation IDs you'd like to use (which will cause it to ignore the facility and machineType you've specified), or just "next-available" to let the controller pick one that's available (that matches the machineType and facility you've specified). Here's an example:
+If you'd like to use reserved instances for your cluster, you need to edit your cluster yaml and add a hardwareReservationID field to your PacketMachineTemplates. That field can contain either a comma-separated list of hardware reservation IDs you'd like to use (which will cause it to ignore the facility and machineType you've specified), or just "next-available" to let the controller pick one that's available (that matches the machineType and facility you've specified). Here's an example:
 
 ```yaml
 apiVersion: infrastructure.cluster.x-k8s.io/v1beta1