readme language

README.md

@@ -6,7 +6,7 @@ The `traefik` dashboard and management endpoint is bound to the private IP of th
 
 Any elastic IPs you add to the instance this provisions will be automatically added to the loopback of the host, which `traefik` will listen on. So if you add an elastic Global IP in the Packet portal to this device, the load balancer will be available on that IP automatically.
 
-In order to add hostnames for `Let's Encrypt` certs to "just work," add device tags to the load balancer device that gets provisioned in the format `hostname=www.mydomain.com`. Make sure that your domain has an A record pointed to an IP attached to your LB device (either the public management IP or an attached elastic IP). If the ACME challenge process fails due to a DNS resolution error (you added the A record after adding the device tag), just remove the hostname tag and re-add it. By default, your LB will be accessible at `<device-short-id>.packethost.net` where `<device-short-id>` is the first section (split on `-`) of your Packet device's ID, with a valid cert.
+In order to add hostnames for `Let's Encrypt` certs to "just work," add device tags to the load balancer device that gets provisioned in the format `hostname=www.mydomain.com`. Make sure that your domain has an A record with an IP attached to your LB device (either the public management IP or an attached elastic IP). If the ACME challenge process fails due to a DNS resolution error (you added the A record after adding the device tag), just remove the hostname tag and re-add it. By default, your LB will be accessible at `<device-short-id>.packethost.net` where `<device-short-id>` is the first section (split on `-`) of your Packet device's ID, with a valid cert.
 
 #### What you get
 - Automatic backend configuration via tags on Packet devices (add/remove backends by adding/removing tags on your Packet device)