qubes-windows-tools currently only exists in the dom0 current-testing repo. According to the dom0 file /etc/yum.repos.d/qubes-dom0.repo, it seems this is by design. If you would prefer to add the package to the current repo instead of this change, that is fine by me. I just wanted to note this in the docs for the next person.
`curl -s yum.qubes-os.org/r3.1/current/dom0/fc20/rpm | grep qubes-windows-tools`
returns nothing
However, current-testing does have it in there:
```
curl -s yum.qubes-os.org/r3.1/current-testing/dom0/fc20/rpm | grep qubes-windows-tools
<li><a href="qubes-windows-tools-3.0.3-1.x86_64.rpm"> qubes-windows-tools-3.0.3-1.x86_64.rpm</a></li>
<li><a href="qubes-windows-tools-3.0.4-1.x86_64.rpm"> qubes-windows-tools-3.0.4-1.x86_64.rpm</a></li>
```
maybe this method should be added as a general point.
e.g.: "Simulating qubes features for vms without qubes support"
a similar thing could be done for windows hvms, too.
you could use teamviewer or vnc and get audio this way (though i don't know whether vnc can stream audio).
* Denoted the edited lines in the pacman.conf output
* Added 'known issues' and 'want to contribute' sections
* For image links I followed the path format used in the doc-guidelines.md ( know the images show up in the webpage when its live but links in the actual .md file thru github)
* Fixed a couple format and typos
Is there anything else that should be edited?
* Fixed: line 191 - typo
* Fixed: line 342 - removed the rpm transfer
line 351 - removed corresponding image-25
* Still Open: line 402-523 - denoting pacman.conf lines that need to be changed within the entire file output.
Replaced short orginal intro and link to the dated developer's section template example with step by step instructions as discussed in the devel mailing list. I have reviewed the steps and checked the text but please review and make any changes/corrections as needed.
