Modified 2 files

Author: rexgnu

docs/1. Introduction/a.interacting-with-the-settle-api.md

@@ -29,12 +29,9 @@ Creating, Retrieving, Updating and Deleting resources, aka **CRUD**, are achiev
 - A detail endpoint looks like `/my_resource/{id}/` where `{id}` is the unique ID of the resource residing at this endpoint.
 
 
-### Examples
-
-> #### Info
->
-> All URLs have a trailing slash by convention.
+> All URLs need a trailing slash 
 
+### Examples
 ```text title="A list endpoint for POS 👇"
 https://api.settle.eu/merchant/v1/pos/
 
@@ -58,8 +55,7 @@ https://api.settle.eu/merchant/v1/pos/3y987j9o4o23/
 /merchant/v1/pos/
 ```
 
-> #### Info
-> For brevity's sake, our documentation will sometimes omit the version bit when specifying endpoint URLs, so `/merchant/v1/` would thus become `/pos/`.
+> For the sake of brevity, the documentation will sometimes omit the version bit when specifying endpoint URLs, so `/merchant/v1/pos/` would then be written as `/pos/`.
 
 ####
 
@@ -308,12 +304,10 @@ Clients are expected to include media type in the `Accept` header listing types
 
 ## A Note on Settle API Users
 
-All requests to the Settle API must include an `X-Settle-User` header.
+All merchant requests to the Settle API must include an `X-Settle-User` header.
 
 <!-- theme: warning -->
-> #### Exception
->
-> Except when an Integrator is acting as a proxy on behalf of a Merchant client. In that case, the `X-Settle-Integrator` header is used instead. [See above](#a-note-on-settle-api-users).
+> When an Integrator is acting as a proxy on behalf of a Merchant client the `X-Settle-Integrator` header is used instead. [See above](#a-note-on-settle-api-users).
 
 API Users are assigned and created by the Merchant through the Settle for Business portal, or by the Integrator using the user endpoint.
 

docs/1. Introduction/b.api-authentication.md

@@ -66,8 +66,6 @@ X-Settle-Timestamp | 	The current UTC time. The time format is `YYYY-MM-DD hh:mm
 X-Settle-Content-Digest | The base64 encoded hash digest of the request body. If the body is empty, the hash should be computed on an empty string.<br><br>The value of the header should be on the form algorithm **UPPERCASE={digest value}**. So, if the **SHA256** hashing algorithm is used on a request with empty body, the header will be:<br><br>`X-Settle-Content-Digest: SHA256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=`
 
 <!-- theme: warning -->
-> Note
->
 > Currently only the **SHA256** hashing algorithm is supported.