edit README

README.md

@@ -24,7 +24,7 @@ The core `runner` logic (capturing and discarding program output) is useful when
 
 ### Containers
 
-`runner` 2.0.0 is useful in various containerization applications, even as a container entrypoint, since it can run a target program in the container, retry it if need be, and capture its output, and send the output via email, ntfy, or Discord. Email, ntfy, and Discord outputs can be configured by the image's end user via environment variables, requiring no build-time customization.
+`runner` 2+ is useful in various containerization applications, even as a container entrypoint. It can run a target program in the container, retry it if need be, capture its output, and then send the output via email, ntfy, or Discord. Email, ntfy, and Discord outputs can be configured by the image's end user via environment variables, requiring no build-time customization. Regardless of these output delivery options, it can always log the program's result to a file as well.
 
 It can even run the target program as a non-root user, and if `runner` is not the container's entrypoint, you can set environment variables like the following to redirect output to the root process's stdout/stderr: