X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=howto-improve-pve-docs.adoc;h=c0d277e4b83cac42da34435daa8de7d2802b82d7;hp=a7a9abddf694a77ad0f11d3be6a0e2b725b65107;hb=4ccb911c76017fed3c649586c39c7b8b79448619;hpb=a69bfc83f6d2b79e94eeb39781d89b720b4482dc

diff --git a/howto-improve-pve-docs.adoc b/howto-improve-pve-docs.adoc
index a7a9abd..c0d277e 100644
--- a/howto-improve-pve-docs.adoc
+++ b/howto-improve-pve-docs.adoc
@@ -8,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
@@ -24,8 +24,8 @@ 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 
-https://git.proxmox.com/?p=pve-docs.git;a=blob_plain;f=README.adoc;hb=HEAD[REAME.adoc] document.
+`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[README.adoc] document.
 
 Improving the documentation is just as easy as editing a Wikipedia
 article and is an interesting foray in the development of a large