all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Oguz Bektas <o.bektas@proxmox.com>
Subject: [pve-devel] applied: SPAM: [PATCH v2 docs] fix typos in various adoc files
Date: Thu, 29 Apr 2021 13:28:00 +0200	[thread overview]
Message-ID: <f6ed7c9a-4fba-aae8-d8c7-be5431d2ac17@proxmox.com> (raw)
In-Reply-To: <20210429110907.426597-1-o.bektas@proxmox.com>

On 29.04.21 13:09, Oguz Bektas wrote:
> checked for common misspellings. some of the changes (like favourite vs.
> favorite or virtualization vs. virtualisation) are because of US vs. UK english
> 
> Reviewed-by: Dylan Whyte <d.whyte@proxmox.com>
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
> v1->v2:
> * fixed up suggestions made by dylan, thanks!
> 
> 
>  certificate-management.adoc |  2 +-
>  local-zfs.adoc              |  6 +++---
>  pve-firewall.adoc           |  2 +-
>  pveceph.adoc                |  8 ++++----
>  pveproxy.adoc               |  2 +-
>  pveum.adoc                  | 13 ++++++-------
>  qm-cloud-init.adoc          | 10 +++++-----
>  qm-pci-passthrough.adoc     |  4 ++--
>  qm.adoc                     | 24 ++++++++++++------------
>  translation.adoc            |  2 +-
>  vzdump.adoc                 |  2 +-
>  11 files changed, 37 insertions(+), 38 deletions(-)
> 
>

applied, thanks to both of you! Note that it'd be also great to adapt touched
stuff to our technical writing guide[0], not all are minimal changes but some
like s/e.g./for example/ would be.

[0]: https://intranet.proxmox.com/index.php/Technical_Writing_Style_Guide




      reply	other threads:[~2021-04-29 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 11:09 [pve-devel] " Oguz Bektas
2021-04-29 11:28 ` Thomas Lamprecht [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=f6ed7c9a-4fba-aae8-d8c7-be5431d2ac17@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=o.bektas@proxmox.com \
    --cc=pve-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal