Update README with recent API changes.

Author: GUI

README.md

@@ -2,7 +2,7 @@
 
 An nginx module to resolve domain names inside upstreams and keep them up to date.
 
-By default, servers defined in nginx upstreams are only resolved when nginx starts. This module provides an alternative `dynamic_server` directive that can be used to asyncronously resolve upstream domain names. This keeps the upstream definition up to date according to the DNS TTL of each domain names. This can be useful if you want to use upstreams for dynamic types of domain names that may frequently change IP addresses.
+By default, servers defined in nginx upstreams are only resolved when nginx starts. This module provides an additional `resolve` parameter for `server` definitions that can be used to asynchronously resolve upstream domain names. This keeps the upstream definition up to date according to the DNS TTL of each domain names. This can be useful if you want to use upstreams for dynamic types of domain names that may frequently change IP addresses.
 
 This module also allows nginx to start if an upstream contains a defunct domain name that no longer resolves. By default, nginx will fail to start if an upstream server contains an unresolvable domain name. With this module, nginx is still allowed to start with invalid domain names, but an error will be logged and the unresolvable domain names will be marked as down.
 
@@ -15,9 +15,9 @@ make && make install
 
 ## Usage
 
-Use the `dynamic_server` definition inside your upstreams instead of the built-in `server` (`dyamic_server` should be a drop-in replacement).
+Use the `server` definition inside your upstreams and specify the `resolve` parameter.
 
-*Note:* A `resolver` must be defined at the `http` level of nginx's config for `dynamic_server` to work.
+*Note:* A `resolver` must be defined at the `http` level of nginx's config for `resolve` to work.
 
 ```
 http {
@@ -31,28 +31,28 @@ http {
 
 ## Directives
 
-### dynamic_server
+### server
 
-**Syntax:** *server address [parameters]*;
-**Context** *upstream*
+**Syntax:** `server address [parameters];`  
+**Context** `upstream`
 
-Defines a server for an upstream. The differences between the default `server` and `dynamic_server` implementation:
+Defines a server for an upstream. The module adds the ability to specify a `resolve` parameter. When specified:
 
 - Domain names will be resolved on an ongoing basis and kept up to date according to the TTL of each domain name.
 - Unresolvable domain names are considered non-fatal errors (but logged). nginx is allowed to startup if a domain name can't be resolved, but the server is marked as down.
 
 The following parameters can be used (see nginx's [server documentation](http://nginx.org/en/docs/http/ngx_http_upstream_module.html#server) for details):
 
-*weight=number*
-*max_fails=number*
-*fail_timeout=time*
-*backup*
-*down*
-*resolve*
+`weight=number`  
+`max_fails=number`  
+`fail_timeout=time`  
+`backup`  
+`down`  
+`resolve`  
 
 # Compatibility
 
-Tested with nginx 1.7.7.
+Tested with nginx 1.6, 1.7, 1.8, 1.9.
 
 ## Alternatives