Skip to content

Commit 7ecf1ab

Browse files
committed
docs(readme): fix typos
1 parent e7215b2 commit 7ecf1ab

1 file changed

Lines changed: 9 additions & 9 deletions

File tree

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,42 +12,42 @@ Multi-platform Docker container with utilities to process Rich Text Format files
1212

1313
## Example without using the filesystem
1414

15-
Let's say that you want to convert an Rich Text Format file intput.rtf in your current working directory to HTML:
15+
Let's say that you want to convert an Rich Text Format file input.rtf in your current working directory to HTML:
1616

1717
**Mac/Linux**
1818

1919
```bash
20-
cat intput.rtf | docker run --rm -i --net=none leplusorg/rst pandoc -f rst -t html - > output.html
20+
cat input.rtf | docker run --rm -i --net=none leplusorg/rst pandoc -f rst -t html - > output.html
2121
```
2222

2323
**Windows**
2424

2525
```batch
26-
type intput.rtf | docker run --rm -i --net=none leplusorg/rst pandoc -f rst -t html - > output.html
26+
type input.rtf | docker run --rm -i --net=none leplusorg/rst pandoc -f rst -t html - > output.html
2727
```
2828

2929
## Example using the filesystem
3030

31-
Same thing, assuming that you want to convert an Rich Text Format file intput.rtf in your current working directory to HTML:
31+
Same thing, assuming that you want to convert an Rich Text Format file input.rtf in your current working directory to HTML:
3232

3333
**Mac/Linux**
3434

3535
```bash
36-
docker run --rm -t --user="$(id -u):$(id -g)" --net=none -v "$(pwd):/tmp" leplusorg/rst pandoc -f rst -t html -o output.html intput.rtf
36+
docker run --rm -t --user="$(id -u):$(id -g)" --net=none -v "$(pwd):/tmp" leplusorg/rst pandoc -f rst -t html -o output.html input.rtf
3737
```
3838

3939
**Windows**
4040

4141
In `cmd`:
4242

4343
```batch
44-
docker run --rm -t --net=none -v "%cd%:/tmp" leplusorg/rst pandoc -f rst -t html -o output.html intput.rtf
44+
docker run --rm -t --net=none -v "%cd%:/tmp" leplusorg/rst pandoc -f rst -t html -o output.html input.rtf
4545
```
4646

4747
In PowerShell:
4848

4949
```pwsh
50-
docker run --rm -t --net=none -v "${PWD}:/tmp" leplusorg/rst pandoc -f rst -t html -o output.html intput.rtf
50+
docker run --rm -t --net=none -v "${PWD}:/tmp" leplusorg/rst pandoc -f rst -t html -o output.html input.rtf
5151
```
5252

5353
## Software Bill of Materials (SBOM)
@@ -74,11 +74,11 @@ docker buildx imagetools inspect leplusorg/rtf --format '{{ json .Provenance }}'
7474

7575
[Sigstore](https://docs.sigstore.dev) is trying to improve supply
7676
chain security by allowing you to verify the origin of an
77-
artifcat. You can verify that the image that you use was actually
77+
artifact. You can verify that the image that you use was actually
7878
produced by this repository. This means that if you verify the
7979
signature of the Docker image, you can trust the integrity of the
8080
whole supply chain from code source, to CI/CD build, to distribution
81-
on Maven Central or whever you got the image from.
81+
on Maven Central or wherever you got the image from.
8282

8383
You can use the following command to verify the latest image using its
8484
sigstore signature attestation:

0 commit comments

Comments
 (0)