IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
This seem wrong,
it's possible to setup management vlan interface
on vlanaware bridge without conflict with vm.
(If vlan management is setup with vmbrX.Y)
Also :
* explain more clearly when PVE switched to persistent device naming. (5.0)
* use eno1 instead of eno0 everywhere when refering to the first onboard device
* use IP addresses from the range IPv4 Address Blocks for Documentation
(rfc5737) instead of private IPv4 addresses when giving examples of public IPs
ddouble words found with /(\b\S+\b)\s+\b\1\b/
(the silver searcher `ag` can find matches even with newlines in
between without extra flags)
Adapt some wording when touching the lines.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
especially:
- filesystem -> file system
- mountpoint -> mount point
- lxc -> LXC
- pve -> PVE
- it's -> its (where appropriate)
- VM´s -> VMs (and similar)
- Ressource -> Resource
- maximal -> maximum or at most
- format of section headers and block headers
reformat most existing 'text' as either `text` or ``text''
reformat most existing "text" as either ``text'' or `text`
reformat 'x' as `x`
harmonize bullet list syntax to use '*' instead of '-'
