Change Auto-Acknowledge to Auto Acknowledge in docs

docs/getting-started.rst

@@ -77,11 +77,11 @@ If, however, you will physically interact with the device, or it has a timer fun
 
 In the example above you can see a function node that has been created to intercept MQTT messages for the device and "translate" them to the required format to send back to Node-RED Smart Home Control.
 
-Auto-Acknowledge
+Auto Acknowledge
 ***************
-So, you're feeling brave? By default, when you add an "alexa-smart-home-v3" node to a flow it is configured for Auto-Acknowledge, this means that a response is sent back to the web API confirming that the command has been received, and it is **assumed** that the command was successful. This may not be desirable, depending upon the criticality of the command you have issued.
+So, you're feeling brave? By default, when you add an "alexa-smart-home-v3" node to a flow it is configured for Auto Acknowledge, this means that a response is sent back to the web API confirming that the command has been received, and it is **assumed** that the command was successful. This may not be desirable, depending upon the criticality of the command you have issued.
 
-It is possible to disable Auto-Acknowledge and use your own logic to establish whether the command was successful, before setting `msg.acknowledge` to `true` or `false` and sending the message to a `alexa-smart-home-v3-resp` node. Note that you must send the **original** message, as output from the "alexa-smart-home-v3" node, modified to include msg.acknowledge.
+It is possible to disable Auto Acknowledge and use your own logic to establish whether the command was successful, before setting `msg.acknowledge` to `true` or `false` and sending the message to a `alexa-smart-home-v3-resp` node. Note that you must send the **original** message, as output from the "alexa-smart-home-v3" node, modified to include msg.acknowledge.
 
 .. image:: concept-response.png
     :width: 606px