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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
They are major sections, equal to "Users" so do not make them a sub
section of "Users" but rather their own. This makes both also visible
in the full admin guide TOC.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
also expand the text a bit, mostly for formatting reasons, as else
the screenshot renders into the CLI pveum code example block in the
HTML output...
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
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>
As inheritance is a property of paths, so it makes sense to
make them a subsection of them.
The permissions paragraph in what used to be a 'terms and
definitions' section now doesn't fit in and is redundant now
that there's a general introduction paragraph.
It now gets more technical to finish the documentation of
the permission checks found in the API documentation, and is
the final section about the various parts making up the
access control lists.
As they provide an overview of predefined roles and give an
idea of what kind of permissions are available, they fit
better right after the new general permission introduction.
You now first read about users, learning the fact that
they're part of groups and realms, which are described
afterwards.
This seems more natural then starting with realms and then
describing users in a "Terms and Definitions" section.
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 '-'
text in backquotes (`) is not subject to asciidoc expansion but
text inside single quotes (') is
this behaviour led that '{vmid}' was somehow interpreted by asciidoc,
and the whole line was not not rendered
pveum.adoc was the only file with that problem as curly brackets
are inside backticks in the rest of the documentation
