From: Dylan Whyte <d.whyte@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH docs] Change "data store" to "datastore" throughout docs
Date: Tue, 8 Sep 2020 11:07:07 +0200 [thread overview]
Message-ID: <20200908090707.11643-1-d.whyte@proxmox.com> (raw)
Before, there were mixed usages of "data store" and
"datastore" throughout the docs.
This improves consistency in the docs by using only
"datastore" throughout.
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
docs/administration-guide.rst | 14 +++++++-------
docs/introduction.rst | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/docs/administration-guide.rst b/docs/administration-guide.rst
index e1a67602..ca7541d4 100644
--- a/docs/administration-guide.rst
+++ b/docs/administration-guide.rst
@@ -261,7 +261,7 @@ Creating a Datastore
.. image:: images/screenshots/pbs-gui-datastore-create-general.png
:width: 230
:align: right
- :alt: Create a data store
+ :alt: Create a datastore
You can create a new datastore from the web GUI, by navigating to **Datastore** in
the menu tree and clicking **Create**. Here:
@@ -528,15 +528,15 @@ You can monitor the roles of each user using the following command:
│ john@pbs │ /datastore/disk1 │ 1 │ DatastoreAdmin │
└──────────┴──────────────────┴───────────┴────────────────┘
-A single user can be assigned multiple permission sets for different data stores.
+A single user can be assigned multiple permission sets for different datastores.
.. Note::
- Naming convention is important here. For data stores on the host,
+ Naming convention is important here. For datastores on the host,
you must use the convention ``/datastore/{storename}``. For example, to set
- permissions for a data store mounted at ``/mnt/backup/disk4/store2``, you would use
+ permissions for a datastore mounted at ``/mnt/backup/disk4/store2``, you would use
``/datastore/store2`` for the path. For remote stores, use the convention
``/remote/{remote}/{storename}``, where ``{remote}`` signifies the name of the
- remote (see `Remote` below) and ``{storename}`` is the name of the data store on
+ remote (see `Remote` below) and ``{storename}`` is the name of the datastore on
the remote.
Network Management
@@ -700,7 +700,7 @@ Garbage Collection
You can monitor and run :ref:`garbage collection <garbage-collection>` on the
Proxmox Backup Server using the ``garbage-collection`` subcommand of
``proxmox-backup-manager``. You can use the ``start`` subcommand to manually start garbage
-collection on an entire data store and the ``status`` subcommand to see
+collection on an entire datastore and the ``status`` subcommand to see
attributes relating to the :ref:`garbage collection <garbage-collection>`.
@@ -1310,7 +1310,7 @@ Garbage Collection
~~~~~~~~~~~~~~~~~~
The ``prune`` command removes only the backup index files, not the data
-from the data store. This task is left to the garbage collection
+from the datastore. This task is left to the garbage collection
command. It is recommended to carry out garbage collection on a regular basis.
The garbage collection works in two phases. In the first phase, all
diff --git a/docs/introduction.rst b/docs/introduction.rst
index 0b0e3ae3..e2953134 100644
--- a/docs/introduction.rst
+++ b/docs/introduction.rst
@@ -22,7 +22,7 @@ Architecture
------------
Proxmox Backup Server uses a `client-server model`_. The server stores the
-backup data and provides an API to create and manage data stores. With the
+backup data and provides an API to create and manage datastores. With the
API, it's also possible to manage disks and other server-side resources.
The backup client uses this API to access the backed up data. With the command
--
2.20.1
next reply other threads:[~2020-09-08 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 9:07 Dylan Whyte [this message]
2020-09-08 11:11 ` [pbs-devel] applied: " Dietmar Maurer
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=20200908090707.11643-1-d.whyte@proxmox.com \
--to=d.whyte@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