Change ambiguous PUT description in api-rest.md

From my point of view, the word `standard` could be interpreted as "usual/common" but also as "specification-standard" (see #198 ). Therefore I'd propose to change it to the word "common".

Author: Otto-AA

api-rest.md

@@ -271,7 +271,7 @@ More examples can be found in the LDP [Primer document](http://www.w3.org/TR/ldp
 
 #### HTTP PUT to create
 
-An alternative (though not standard) way of creating new resources is to use
+An alternative (though not common) way of creating new resources is to use
 HTTP PUT. Although HTTP PUT is commonly used to overwrite resources, this way is
 usually preferred when creating new non-RDF resources (i.e. using a mime type
 different than `text/turtle`).
@@ -392,4 +392,4 @@ Servers SHOULD send a WAC-Allow response header on HEAD and GET, with a value li
 ```http
 WAC-Allow: user="read write append control",public="read"
 ```
-In general, the format is `user="` + user-permissions = `",public="` + public-permissions + `"`. User-permissions and public-permissions should both be space-separated lists, containing a subset of ['read', 'write', 'append', 'control']. If 'write' is present then 'append' should also be present.
+In general, the format is `user="` + user-permissions = `",public="` + public-permissions + `"`. User-permissions and public-permissions should both be space-separated lists, containing a subset of ['read', 'write', 'append', 'control']. If 'write' is present then 'append' should also be present.