proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-06-15 03:40:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

readme: fix typos

Browse Source
This commit is contained in:
Fabian Grünbichler 2016-09-23 13:58:45 +02:00
parent 05a63379b6
commit 128b18c0e5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.adoc
View File

@ -10,7 +10,7 @@ The basic idea is to generate high quality manual pages, and assemble
them into a complete book, called link:pve-admin-guide.adoc[Proxmox VE them into a complete book, called link:pve-admin-guide.adoc[Proxmox VE
Administration Guide]. So we have one source, and generate several Administration Guide]. So we have one source, and generate several
documents from that. It is also possible to generate printable PDF documents from that. It is also possible to generate printable PDF
files, or ebook formats ('.ebup'). files, or ebook formats ('.epub').
When possible, we provide scripts to extract API definitions, When possible, we provide scripts to extract API definitions,
configuration or command line options from the source code. configuration or command line options from the source code.
@ -176,11 +176,11 @@ Text and Block Styles
* 'Emphasized text': created using \'text', used for emphasizing words * 'Emphasized text': created using \'text', used for emphasizing words
and phrases and phrases
* `Monospaced text`: created using \`text`, used for command / program * `Monospaced text`: created using \`text`, used for command / program
names, file paths, inline commands, option names and values names, file paths, in-line commands, option names and values
* *Strong text*: created using \*text*, used for emphasizing concepts * *Strong text*: created using \*text*, used for emphasizing concepts
or names when first introduced in a section. or names when first introduced in a section.
There are also different builtin block styles that are used in There are also different built-in block styles that are used in
our documentation: our documentation:
Complete paragraphs can be included literally by prepending each Complete paragraphs can be included literally by prepending each