docs(readme): fix typos

Author: thomasleplus

README.md

@@ -12,42 +12,42 @@ Multi-platform Docker container with utilities to process Mardown and text files
 
 ## Example without using the filesystem
 
-Let's say that you want to convert an Markdown file intput.md in your current working directory to HTML:
+Let's say that you want to convert an Markdown file input.md in your current working directory to HTML:
 
 **Mac/Linux**
 
 ```bash
-cat intput.md | docker run --rm -i --net=none leplusorg/md pandoc -o - > output.html
+cat input.md | docker run --rm -i --net=none leplusorg/md pandoc -o - > output.html
 ```
 
 **Windows**
 
 ```batch
-type intput.md | docker run --rm -i --net=none leplusorg/md pandoc -o - > output.html
+type input.md | docker run --rm -i --net=none leplusorg/md pandoc -o - > output.html
 ```
 
 ## Example using the filesystem
 
-Same thing, assuming that you want to convert an Markdown file intput.md in your current working directory to HTML:
+Same thing, assuming that you want to convert an Markdown file input.md in your current working directory to HTML:
 
 **Mac/Linux**
 
 ```bash
-docker run --rm -t --user="$(id -u):$(id -g)" --net=none -v "$(pwd):/tmp" leplusorg/md pandoc -o output.html intput.md
+docker run --rm -t --user="$(id -u):$(id -g)" --net=none -v "$(pwd):/tmp" leplusorg/md pandoc -o output.html input.md
 ```
 
 **Windows**
 
 In `cmd`:
 
 ```batch
-docker run --rm -t --net=none -v "%cd%:/tmp" leplusorg/md pandoc -o output.html intput.md
+docker run --rm -t --net=none -v "%cd%:/tmp" leplusorg/md pandoc -o output.html input.md
 ```
 
 In PowerShell:
 
 ```pwsh
-docker run --rm -t --net=none -v "${PWD}:/tmp" leplusorg/md pandoc -o output.html intput.md
+docker run --rm -t --net=none -v "${PWD}:/tmp" leplusorg/md pandoc -o output.html input.md
 ```
 
 ## NPM Packages
@@ -80,11 +80,11 @@ docker buildx imagetools inspect leplusorg/md --format '{{ json .Provenance }}'
 
 [Sigstore](https://docs.sigstore.dev) is trying to improve supply
 chain security by allowing you to verify the origin of an
-artifcat. You can verify that the image that you use was actually
+artifact. You can verify that the image that you use was actually
 produced by this repository. This means that if you verify the
 signature of the Docker image, you can trust the integrity of the
 whole supply chain from code source, to CI/CD build, to distribution
-on Maven Central or whever you got the image from.
+on Maven Central or wherever you got the image from.
 
 You can use the following command to verify the latest image using its
 sigstore signature attestation: