buildsys: don't use rm -r on so many globs

[pve-docs.git] / howto-improve-pve-docs.adoc

diff --git a/howto-improve-pve-docs.adoc b/howto-improve-pve-docs.adoc
index 4e9bec2b28940c02e058399cf2a1792970914193..557e010c30938ffcca93a78a01479160111a2b93 100644 (file)
--- a/howto-improve-pve-docs.adoc
+++ b/howto-improve-pve-docs.adoc
@@ -1,7 +1,6 @@
 [[howto_improve_pve_docs]]
 Improving the Proxmox VE Documentation
 --------------------------------------
-include::attributes.txt[]
 ifdef::wiki[]
 :pve-toplevel:
 endif::wiki[]
@@ -9,8 +8,8 @@ endif::wiki[]
 Depending on which issue you want to improve, you can use a variety of
 communication mediums to reach the developers.
 
-If you notice an error in the current documentation, use the·
-http://bugzilla.proxmox.com[Proxmox bug tracker] and propose an·
+If you notice an error in the current documentation, use the
+http://bugzilla.proxmox.com[Proxmox bug tracker] and propose an
 alternate text/wording.
 
 If you want to propose new content, it depends on what you want to
@@ -25,7 +24,7 @@ OS, this is a perfect fit for a wiki article.
 then you should try to get it into the reference documentation. The reference
 documentation is written in the easy to use 'asciidoc' document format.
 Editing the official documentation requires to clone the git repository at
-`git://git.proxmox.com/git/pve-docs.git` and then follow the 
+`git://git.proxmox.com/git/pve-docs.git` and then follow the
 https://git.proxmox.com/?p=pve-docs.git;a=blob_plain;f=README.adoc;hb=HEAD[REAME.adoc] document.
 
 Improving the documentation is just as easy as editing a Wikipedia