docs: fix some typos
the `congestion` typo has been mentioned in the forum: https://forum.proxmox.com/threads/proxmox-backup-server-2-1-released.100240/#post-443370 fixed a few surrounding ones and ones that `codespell` found in addition to that. Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
d43aca148f
commit
c10a6755f0
|
@ -71,7 +71,7 @@ Environment Variables
|
|||
|
||||
|
||||
.. Note:: Passwords must be valid UTF-8 and may not contain newlines. For your
|
||||
convienience, Proxmox Backup Server only uses the first line as password, so
|
||||
convenience, Proxmox Backup Server only uses the first line as password, so
|
||||
you can add arbitrary comments after the first newline.
|
||||
|
||||
|
||||
|
|
|
@ -117,9 +117,9 @@ The same filter is applied to local groups for handling of the
|
|||
Bandwidth Limit
|
||||
^^^^^^^^^^^^^^^
|
||||
|
||||
Syncing datastores to an archive can produce lots of traffic and impact other
|
||||
users of the network. So, to avoid network or storage congetsion you can limit
|
||||
the bandwith of the sync job by setting the ``rate-in`` option either in the
|
||||
Syncing a datastore to an archive can produce lots of traffic and impact other
|
||||
users of the network. So, to avoid network or storage congestion you can limit
|
||||
the bandwidth of the sync job by setting the ``rate-in`` option either in the
|
||||
web interface or using the ``proxmox-backup-manager`` command-line tool:
|
||||
|
||||
.. code-block:: console
|
||||
|
|
|
@ -21,7 +21,7 @@ You can manage the traffic controls either over the web-interface or using the
|
|||
tool.
|
||||
|
||||
.. note:: Sync jobs on the server are not affected by its rate-in limits. If
|
||||
you want to limit the incomming traffic that a pull-based sync job
|
||||
you want to limit the incoming traffic that a pull-based sync job
|
||||
generates, you need to setup a job-specific rate-in limit. See
|
||||
:ref:`syncjobs`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue