ENT-4165 Use PATCH method in settings API example

Patch is more usable since you do not have to provide the complete settings. For
one-liner commands and examples using PATCH should be much better.

examples/enterprise-api-examples/managing-settings.markdown

@@ -42,10 +42,7 @@ are managed by the LDAP API and not this Settings API.
 
 **Request**
 
-    curl --user admin:admin http://test.cfengine.com/api/settings -X POST -d
-    {
-      "ldapEnabled": true
-    }
+    curl --user admin:admin http://test.cfengine.com/api/settings -X PATCH -d '{ "ldapEnabled": true }'
 
 **Response**
 
@@ -57,15 +54,14 @@ are managed by the LDAP API and not this Settings API.
 The API uses standard Unix syslog to log a number of events. Additionally, log
 events are sent to `stderr`, which means they may also end up in your Apache
 log. Log events are filtered based on the log level in settings. Suppose you
-wanted to have greater visibility into the processing done at the backend. The
+wanted to have greater visibility into the processing done at the back-end. The
 standard log level is `error`. Changing it to `info` is done as follows.
 
+**NOTE:** Change to API log level will only take effect after Apache has re-started.
+
 **Request**
 
-    curl --user admin:admin http://test.cfengine.com/api/settings -X POST -d
-    {
-      "logLevel": "info"
-    }
+    curl --user admin:admin http://test.cfengine.com/api/settings -X PATCH -d '{ "logLevel": "info" }'
 
 **Response**