[pbs-devel] [PATCH proxmox-backup] docs: fix typos in maintenance section

[pbs-devel] [PATCH proxmox-backup] docs: fix typos in maintenance section

[Oguz Bektas]

Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
---
 docs/maintenance.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/maintenance.rst b/docs/maintenance.rst
index 561b4fe4..8a90d5f6 100644
--- a/docs/maintenance.rst
+++ b/docs/maintenance.rst
@@ -48,7 +48,7 @@ Prune Simulator
 ^^^^^^^^^^^^^^^
 
 You can use the built-in `prune simulator <prune-simulator/index.html>`_
-to explore the effect of different retetion options with various backup
+to explore the effect of different retention options with various backup
 schedules.
 
 Manual Pruning
@@ -147,13 +147,13 @@ snapshots are ignored, as well as set a time period, after which verified jobs
 are checked again. The interface for creating verify jobs can be found under the
 **Verify Jobs** tab of the datastore.
 
-.. Note:: It is recommended that you reverify all backups at least monthly, even
-  if a previous verification was successful. This is becuase physical drives
+.. Note:: It is recommended that you re-verify all backups at least monthly, even
+  if a previous verification was successful. This is because physical drives
   are susceptible to damage over time, which can cause an old, working backup
   to become corrupted in a process known as `bit rot/data degradation
   <https://en.wikipedia.org/wiki/Data_degradation>`_. It is good practice to
   have a regularly recurring (hourly/daily) verification job, which checks new
-  and expired backups, then another weekly/monthly job that will reverify
+  and expired backups, then another weekly/monthly job that will re-verify
   everything. This way, there will be no surprises when it comes to restoring
   data.
 
-- 
2.20.1

Re: [pbs-devel] [PATCH proxmox-backup] docs: fix typos in maintenance section

[Thomas Lamprecht]

On 24.11.20 11:52, Oguz Bektas wrote:
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
>  docs/maintenance.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

thanks, a comment about reverify below  

> diff --git a/docs/maintenance.rst b/docs/maintenance.rst
> index 561b4fe4..8a90d5f6 100644
> --- a/docs/maintenance.rst
> +++ b/docs/maintenance.rst
> @@ -48,7 +48,7 @@ Prune Simulator
>  ^^^^^^^^^^^^^^^
>  
>  You can use the built-in `prune simulator <prune-simulator/index.html>`_
> -to explore the effect of different retetion options with various backup
> +to explore the effect of different retention options with various backup
>  schedules.
>  
>  Manual Pruning
> @@ -147,13 +147,13 @@ snapshots are ignored, as well as set a time period, after which verified jobs
>  are checked again. The interface for creating verify jobs can be found under the
>  **Verify Jobs** tab of the datastore.
>  
> -.. Note:: It is recommended that you reverify all backups at least monthly, even
> -  if a previous verification was successful. This is becuase physical drives
> +.. Note:: It is recommended that you re-verify all backups at least monthly, even


"reverify" seems to be just fine though, at least I find so many references
in various dictionaries/articles that I do not think this requires change.

https://www.dict.cc/?s=reverify
https://dict.leo.org/englisch-deutsch/reverify
https://en.wiktionary.org/wiki/reverify
https://en.wikipedia.org/wiki/Reverification

> +  if a previous verification was successful. This is because physical drives
>    are susceptible to damage over time, which can cause an old, working backup
>    to become corrupted in a process known as `bit rot/data degradation
>    <https://en.wikipedia.org/wiki/Data_degradation>`_. It is good practice to
>    have a regularly recurring (hourly/daily) verification job, which checks new
> -  and expired backups, then another weekly/monthly job that will reverify
> +  and expired backups, then another weekly/monthly job that will re-verify

same here

>    everything. This way, there will be no surprises when it comes to restoring
>    data.
>  
>