Formatted the document in a more structured table listing the known use cases.
- Separated the network utilities from the standard util packages
- Removed the ProxyVM section completely, as it didn't add much information
- Moved the logging information to an ending section, where more topics can be listed.
Expanded the description of a standard NetVM with qubes-input-proxy-sender, so that a 3.2 standard installation with NetVM=UsbVM does not leave USB broken when replacing the NetVM template with the fedora-minimal one.
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.
