From aa96a95600cc475ad93eb96e9bb3b68a6488798f Mon Sep 17 00:00:00 2001 From: cupcakearmy Date: Wed, 21 Apr 2021 09:34:01 +0200 Subject: [PATCH] typos --- docs/markdown/backend/overview.md | 2 +- docs/markdown/location/cron.md | 10 +++++----- docs/markdown/location/exclude.md | 2 +- docs/markdown/location/forget.md | 10 +++++----- docs/markdown/location/overview.md | 2 +- docs/markdown/quick.md | 2 +- 6 files changed, 14 insertions(+), 14 deletions(-) diff --git a/docs/markdown/backend/overview.md b/docs/markdown/backend/overview.md index 0f0baa5..e0d4aae 100644 --- a/docs/markdown/backend/overview.md +++ b/docs/markdown/backend/overview.md @@ -1,6 +1,6 @@ # 💽 Backends -Backends are the ouputs of the backup process. Each location needs at least one. +Backends are the outputs of the backup process. Each location needs at least one. ```yaml | .autorestic.yml backends: diff --git a/docs/markdown/location/cron.md b/docs/markdown/location/cron.md index 3557462..3d623c1 100644 --- a/docs/markdown/location/cron.md +++ b/docs/markdown/location/cron.md @@ -1,6 +1,6 @@ # Cron -Often it is usefull to trigger backups autmatically. For this we can specify a `cron` attribute to each location. +Often it is usefully to trigger backups automatically. For this we can specify a `cron` attribute to each location. ```yaml | .autorestic.yml locations: @@ -14,11 +14,11 @@ Here is a awesome website with [some examples](https://crontab.guru/examples.htm ## Installing the cron -**This has to be done only once, regadless of now many cros you have in your config file.** +**This has to be done only once, regardless of now many cron jobs you have in your config file.** -To actually enable cron jobs you need something to call `autorestic cron` on a timed shedule. -Note that the shedule has nothing to do with the `cron` attribute in each location. -My advise would be to trigger the command every 5min, but if you have a cronjob that runs only once a week, it's probably enough to shedule it once a day. +To actually enable cron jobs you need something to call `autorestic cron` on a timed schedule. +Note that the schedule has nothing to do with the `cron` attribute in each location. +My advise would be to trigger the command every 5min, but if you have a cronjob that runs only once a week, it's probably enough to schedule it once a day. ### Crontab diff --git a/docs/markdown/location/exclude.md b/docs/markdown/location/exclude.md index 0bd1337..775f8f1 100644 --- a/docs/markdown/location/exclude.md +++ b/docs/markdown/location/exclude.md @@ -1,6 +1,6 @@ # Excluding files -If you want to exclude certain files or folders it done easily by specifiyng the right flags in the location you desire to filter. +If you want to exclude certain files or folders it done easily by specifying the right flags in the location you desire to filter. The flags are taken straight from the [restic cli exclude rules](https://restic.readthedocs.io/en/latest/040_backup.html#excluding-files) so you can use any flag used there. diff --git a/docs/markdown/location/forget.md b/docs/markdown/location/forget.md index 52d617d..ad17c2c 100644 --- a/docs/markdown/location/forget.md +++ b/docs/markdown/location/forget.md @@ -14,11 +14,11 @@ locations: options: forget: keep-last: 5 # always keep at least 5 snapshots - keep-hourly: 3 # keep 3 last hourly shapshots - keep-daily: 4 # keep 4 last daily shapshots - keep-weekly: 1 # keep 1 last weekly shapshots - keep-monthly: 12 # keep 12 last monthly shapshots - keep-yearly: 7 # keep 7 last yearly shapshots + keep-hourly: 3 # keep 3 last hourly snapshots + keep-daily: 4 # keep 4 last daily snapshots + keep-weekly: 1 # keep 1 last weekly snapshots + keep-monthly: 12 # keep 12 last monthly snapshots + keep-yearly: 7 # keep 7 last yearly snapshots keep-within: '2w' # keep snapshots from the last 2 weeks ``` diff --git a/docs/markdown/location/overview.md b/docs/markdown/location/overview.md index 230415b..c92a7e0 100644 --- a/docs/markdown/location/overview.md +++ b/docs/markdown/location/overview.md @@ -22,6 +22,6 @@ Paths can be absolute or relative. If relative they are resolved relative to the ## `to` -This is einther a single backend or an array of backends. The backends have to be configured in the same config file. +This is either a single backend or an array of backends. The backends have to be configured in the same config file. > :ToCPrevNext diff --git a/docs/markdown/quick.md b/docs/markdown/quick.md index 0ad1c18..16f98af 100644 --- a/docs/markdown/quick.md +++ b/docs/markdown/quick.md @@ -15,7 +15,7 @@ vim .autorestic.yml For a quick overview: - `locations` can be seen as the inputs and `backends` the output where the data is stored and backed up. -- One `location` can have one or multiple `backends` for redudancy. +- One `location` can have one or multiple `backends` for redundancy. - One `backend` can also be the target for multiple `locations`. > **⚠️ WARNING ⚠️**