public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH backup] fix typos in docs and API descriptions
Date: Wed, 22 Jan 2025 15:21:06 +0100	[thread overview]
Message-ID: <D78O2TMNUHBF.9EJF8X1FS1UG@proxmox.com> (raw)
In-Reply-To: <20250122133729.329525-1-m.sandoval@proxmox.com>

On Wed Jan 22, 2025 at 2:37 PM CET, Maximiliano Sandoval wrote:
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
>  docs/storage.rst                       | 4 ++--
>  docs/technical-overview.rst            | 2 +-
>  src/bin/proxmox_backup_manager/cert.rs | 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/docs/storage.rst b/docs/storage.rst
> index 2c53dca81..e43d7ea4c 100644
> --- a/docs/storage.rst
> +++ b/docs/storage.rst
> @@ -209,7 +209,7 @@ allowed to be nested.
>  Removable datastores are created on the the device with the given relative path that is specified
>  on creation. In order to use a datastore on multiple PBS instances, it has to be created on one,
>  and added with ``Reuse existing datastore`` checked on the others. The path you set on creation
> -is how multiple datastores on a signle device are identified. So When adding on a new PBS instance,
> +is how multiple datastores on a single device are identified. So When adding on a new PBS instance,

if you touch this line, would you mind changing the "When" here to lower
case as well?

>  it has to match what was set on creation.
>
>  .. code-block:: console
> @@ -231,7 +231,7 @@ All datastores present on a device can be listed using ``proxmox-backup-debug``.
>  Verify, Prune and Garbage Collection jobs are skipped if the removable
>  datastore is not mounted when they are scheduled. Sync jobs start, but fail
>  with an error saying the datastore was not mounted. The reason is that syncs
> -not happening as scheduled should at least be noticable.
> +not happening as scheduled should at least be noticeable.
>
>  Managing Datastores
>  ^^^^^^^^^^^^^^^^^^^
> diff --git a/docs/technical-overview.rst b/docs/technical-overview.rst
> index ac42da3a2..6a76942f1 100644
> --- a/docs/technical-overview.rst
> +++ b/docs/technical-overview.rst
> @@ -147,7 +147,7 @@ in a single ``pxar`` archive, the latter two modes split data and metadata into
>  ``ppxar`` and ``mpxar`` archives. This is done to allow for fast comparison of
>  metadata with the previous snapshot, used by the ``metadata`` mode to detect
>  reusable files. The ``data`` mode refrains from reusing unchanged files by
> -rechunking the file uncoditionally. This mode therefore assures that no file
> +rechunking the file unconditionally. This mode therefore assures that no file
>  changes are missed even if the metadata are unchanged.
>
>  .. NOTE:: ``pxar`` and ``mpxar``/``ppxar`` file formats are different and cannot
> diff --git a/src/bin/proxmox_backup_manager/cert.rs b/src/bin/proxmox_backup_manager/cert.rs
> index 2816e8c0a..c5c1c1b89 100644
> --- a/src/bin/proxmox_backup_manager/cert.rs
> +++ b/src/bin/proxmox_backup_manager/cert.rs
> @@ -48,7 +48,7 @@ fn cert_info() -> Result<(), Error> {
>      input: {
>          properties: {
>              force: {
> -	        description: "Force generation of new SSL certifate.",
> +	        description: "Force generation of new SSL certificate.",
>  	        type:  Boolean,
>  	        optional:true,
>  	    },



_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


      reply	other threads:[~2025-01-22 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 13:37 Maximiliano Sandoval
2025-01-22 14:21 ` Shannon Sterz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D78O2TMNUHBF.9EJF8X1FS1UG@proxmox.com \
    --to=s.sterz@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal