public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/9] package-repos: fix typos
Date: Fri, 18 Nov 2022 12:09:42 +0100	[thread overview]
Message-ID: <20221118110949.59298-2-m.heiserer@proxmox.com> (raw)
In-Reply-To: <20221118110949.59298-1-m.heiserer@proxmox.com>

Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
---
 pve-package-repos.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pve-package-repos.adoc b/pve-package-repos.adoc
index 3237ddf..52169a0 100644
--- a/pve-package-repos.adoc
+++ b/pve-package-repos.adoc
@@ -108,7 +108,7 @@ deb http://security.debian.org/debian-security bullseye-security main contrib
 
 This repository contains the latest packages and is primarily used by developers
 to test new features. To configure it, add the following line to
-`etc/apt/sources.list`:
+`/etc/apt/sources.list`:
 
 .sources.list entry for `pvetest`
 ----
@@ -176,7 +176,7 @@ deb http://download.proxmox.com/debian/ceph-pacific bullseye test
 Ceph Octopus Repository
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-NOTE: Ceph Octopus (15.2) was declared stable with {pve} 6.3 it will continue
+NOTE: Ceph Octopus (15.2) was declared stable with {pve} 6.3. It will continue
 to get updates for the xref:faq-support-table[remaining life time of the 6.x release]
 and also for {pve} 7.x until Ceph Octopus upstream EOL (~ 2022-07).
 
-- 
2.30.2





  reply	other threads:[~2022-11-18 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 11:09 [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Matthias Heiserer
2022-11-18 11:09 ` Matthias Heiserer [this message]
2022-11-18 11:09 ` [pve-devel] [PATCH docs 3/9] network: fix typo Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 4/9] network: fix dead link Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 5/9] local-lvm: typo fix/better phrasing Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 6/9] local-zfs Remove SSD suggestion as it's outdated Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 7/9] local-zfs: rephrase ZFS RAID description Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 8/9] local-zfs: typo fix/better phrasing Matthias Heiserer
2022-11-18 11:09 ` [pve-devel] [PATCH docs 9/9] Update ExtJS version Matthias Heiserer
2022-11-18 12:03 ` [pve-devel] [PATCH docs 1/9] bibliography: update 404 link Thomas Lamprecht
2022-11-18 12:04 ` [pve-devel] applied-series: " 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=20221118110949.59298-2-m.heiserer@proxmox.com \
    --to=m.heiserer@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal