From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container] fix typos on user-visible strings
Date: Fri, 11 Oct 2024 11:40:25 +0200 [thread overview]
Message-ID: <20241011094025.119118-1-m.sandoval@proxmox.com> (raw)
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
src/PVE/API2/LXC.pm | 4 ++--
src/PVE/CLI/pct.pm | 2 +-
src/PVE/LXC/Config.pm | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index 918e719..4657ee1 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -77,7 +77,7 @@ __PACKAGE__->register_method({
method => 'GET',
description => "LXC container index (per node).",
permissions => {
- description => "Only list CTs where you have VM.Audit permissons on /vms/<vmid>.",
+ description => "Only list CTs where you have VM.Audit permission on /vms/<vmid>.",
user => 'all',
},
proxyto => 'node',
@@ -123,7 +123,7 @@ __PACKAGE__->register_method({
description => "Create or restore a container.",
permissions => {
user => 'all', # check inside
- description => "You need 'VM.Allocate' permissions on /vms/{vmid} or on the VM pool /pool/{pool}. " .
+ description => "You need 'VM.Allocate' permission on /vms/{vmid} or on the VM pool /pool/{pool}. " .
"For restore, it is enough if the user has 'VM.Backup' permission and the VM already exists. " .
"You also need 'Datastore.AllocateSpace' permissions on the storage.",
},
diff --git a/src/PVE/CLI/pct.pm b/src/PVE/CLI/pct.pm
index 4504b54..b0a1ec2 100755
--- a/src/PVE/CLI/pct.pm
+++ b/src/PVE/CLI/pct.pm
@@ -533,7 +533,7 @@ __PACKAGE__->register_method ({
type => 'boolean',
optional => 1,
default => 0,
- description => 'Do not actually write changes out to conifg.',
+ description => 'Do not actually write changes to the configuration.',
},
},
},
diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
index ce64c4c..ba50af6 100644
--- a/src/PVE/LXC/Config.pm
+++ b/src/PVE/LXC/Config.pm
@@ -607,7 +607,7 @@ my $confdesc = {
optional => 1,
type => 'string',
format => 'pve-volume-id',
- description => 'Script that will be exectued during various steps in the containers lifetime.',
+ description => 'Script that will be executed during various steps in the containers lifetime.',
},
tags => {
type => 'string', format => 'pve-tag-list',
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-10-11 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 9:40 Maximiliano Sandoval [this message]
2024-10-24 14:53 ` [pve-devel] applied: " Thomas Lamprecht
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=20241011094025.119118-1-m.sandoval@proxmox.com \
--to=m.sandoval@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox