Fix: README: typos

diff --git a/README.md b/README.md
index e0fb43acccdb17866c0c2259892bc1a7567ce9d5..b6591610ae0da4c409c3f748d539e5e58b691b43 100644 (file)
--- a/README.md
+++ b/README.md
@@ -29,7 +29,7 @@ by this one:
 Instead of being just a shorthand, `trashman` packages can try as best as possible
 not to fetch keys and scripts from remote locations without some basic checks. So if
 you have to add files into `/etc/apt/trusted.gpg.d`, `trashman` will provide those
-keys or fingerprints instead of donwloading it from somewhere, in which case it could
+keys or fingerprints instead of downloading it from somewhere, in which case it could
 be easily tampered.
 
 ## Hoarder
@@ -60,7 +60,7 @@ locally, at the current user's folder:
 * Provides basic automation: instead of always running command by hand, recipes
   can be included in your deployment scripts.
 
-* The one to rule then all; a meta package manager suporting any other
+* The one to rule then all; a meta package manager suportting any other
   package manager, like apt/dpkg, stowpkg, pkg_src, etc.
 
 ## Limitations
@@ -72,17 +72,17 @@ locally, at the current user's folder:
 
 * Do not use your main system for installing `trashman` packages. Use a Virtual Machine
   instead: this is more manageable and keep the litter isolated from the other parts
-  of your infostructure.
+  of your infrastructure.
 
 * Not everything can be checked in advance by `trashman` packages. Each package can do
   it's best to check sources and avoiding running unsigned/untrusted code from remote
   locations.
 
-* This software is a poor mitigiation and a way to save yourself some time in a growing
+* This software is a poor mitigation and a way to save yourself some time in a growing
   trend of open source software lifecycles dominated by conglomerates running their
   "cloud" providing you with "open core" applications, taking over your computing stack.
 
-## Instalation
+## Installation
 
 Simply clone it and add to your `$PATH`:
 
@@ -106,7 +106,7 @@ Syncing the codebase is a two-step procedure. First grab upstream changes:
 
     trashman fetch
 
-This will outpupt current OpenPGP signature's from the last commit. You might
+This will output current OpenPGP signature's from the last commit. You might
 check that and also check for repository changes. Once you're fine with those,
 do the actual merge: