Simplify wording on arguments and returned values

Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>

1 files changed, 2 insertions, 8 deletions

diff --git a/README.md b/README.md
index bcc8ec0..b9a3e0b 100644
--- a/README.md
+++ b/README.md
@@ -399,14 +399,8 @@ stack overflows are a real danger here.
 
 It is generally a good idea to reserve some bytes for argument passing. For
 example, one might reserve `$00-$04` to variables named like `zp_arg0` to
-`zp_arg4`. These memory arguments can then be considered like this:
-
-1. It's up to the caller to save values from these addresses if they are to be
-   preserved across calls. The called function might change these values during its
-   execution.
-2. The called function can save to `zp_arg0` the returned value, and also to
-   `zp_arg1` if the returned value is 16 bit (little endian). In any case, and
-   as always, read the documentation for it.
+`zp_arg4`. These memory arguments can then be consumed/owned in different
+ways. In any case, be consistent and document this clearly on each function.
 
 ## Using the `x` or `y` registers for code that has to "select"