Removed verb misconcenption

If an action outside CRUD is needed for a specific resource, it is usually expressed with an POST to an action. For instance, the previous example could be modelled as:

POST /documents/archieveExpired

README.md

@@ -1522,7 +1522,6 @@ REST is focused on exposing data.  It minimizes the coupling between client/serv
 #### Disadvantage(s): REST
 
 * With REST being resource oriented, it demands a solid understanding of the business, so hierarchy and relationships between resources can be properly modeled. A poorly designed API is hard to evolve and misleads future clients implementations.
-* REST typically relies on a few verbs (GET, POST, PUT, DELETE, and PATCH) which sometimes doesn't fit your use case.  For example, moving expired documents to the archive folder might not cleanly fit within these verbs.
 * Fetching complicated resources with nested hierarchies requires multiple round trips between the client and server to render single views, e.g. fetching content of a blog entry and the comments on that entry. For mobile applications operating in variable network conditions, these multiple roundtrips are highly undesirable.
 * Over time, more fields might be added to an API response and older clients will receive all new data fields, even those that they do not need, as a result, it bloats the payload size and leads to larger latencies.