Manual-Decentrale-Validatieservice-(English).md

@@ -6,7 +6,6 @@ Start the docker image normally (e.g., using ``docker run -itp 8080:8080 registr
 
 All requests **must** include a ``Content-Type`` header with value ``application/x-www-form-urlencoded`` and a correct ``Content-Length`` header.
 
-__From version 1.1:__ Calls support a ``X-Version-Override`` header which allows overriding the patch level of the standard.  If no such override, the default patch is used (corresponding to the validation date, not the dagtekening).  If the requested patch level is not/no longer supported an error code 400 is returned.  Note that automatic updates may introduce/remove patch levels, so clients should have a meaningful fallback for unsupported patch levels.
 
 ### Health check ###
 
@@ -30,10 +29,6 @@ Example (standard validation):
 curl -X POST --data-binary @bericht.xml localhost:8080/validatie
 ```
 
-Example (validation with fixed patch version, 3.0.3, version 1.1 and newer only):
-```
-curl -X POST -H "X-Version-Override: 3.0.3" --data-binary @bericht.xml localhost:8080/validatie
-```
 
 ### Generate retourbericht ###
 
@@ -46,10 +41,6 @@ Example (standard generation):
 curl -X POST --data-binary @heenbericht.xml localhost:8080/retour
 ```
 
-Example (generation with fixed patch version, 3.0.3, version 1.1 and newer only):
-```
-curl -X POST -H "X-Version-Override: 3.0.3" --data-binary @heenbericht.xml localhost:8080/retour
-```
 
 ### Error codes ###
 
@@ -61,4 +52,4 @@ curl -X POST -H "X-Version-Override: 3.0.3" --data-binary @heenbericht.xml local
 |  406   | Invalid request; message does not match any schema (unsupported type or technically invalid messsage) | 
 |  411   | Invalid request; must specify a Content-Length header | 
 |  415   | Invalid request; must use Content-Type exactly ``application/x-www-form-urlencoded`` (with no additional data like charset, etc.) |
-|  500   | Something went wrong in the server |
+|  500   | Something went wrong in the server |
\ No newline at end of file