Remove 'Dynamic' from 'Check Deployment' docs

It is indeed dynamic, just want to avoid confusion with
the dynamic data store

README.md

@@ -23,7 +23,7 @@ However, if you want to rely on other roles/management methods to deploy/manage
 This role requires:
 - Ansible 2.0
 - The `dynamic_data_store` variable to be set: see [Dynamic Data Store](http://ansible-sensu.readthedocs.io/en/latest/dynamic_data/)
-- If `sensu_include_plugins` is true (the default), the `static_data_store` variable needs to be set: see [Dynamic Check Deployment](http://ansible-sensu.readthedocs.io/en/latest/dynamic_checks/)
+- If `sensu_include_plugins` is true (the default), the `static_data_store` variable needs to be set: see [Check Deployment](http://ansible-sensu.readthedocs.io/en/latest/dynamic_checks/)
 
 ## Supported Platforms
 ### Current Release

docs/dynamic_checks.md

@@ -1,4 +1,4 @@
-# Dynamic Check Deployment
+# Check Deployment
 One of the awesome features of this role (if I do say so myself) is the deployment of Sensu [checks](https://sensuapp.org/docs/latest/reference/checks) on a dynamic basis. Deployment of which checks should be distributed to which nodes is determined from group membership within the Ansible inventory.
 
 Have a group of webservers you need to monitor webservices on? Well, I'm sure you've bunched them together in your inventory under the `[webservers]` group, right? Or perhaps you only want to monitor disk space on your production systems; if they're a member of `[production]` within the inventory, you can do this easily.