Clarify section on copying to dom0; fix capitalization

user/common-tasks/copy-from-dom0.md

@@ -23,7 +23,7 @@ qvm-copy-to-vm <dest-vm> <file>
 
 The file will arrive in your destination VM in the `~/QubesIncoming/dom0/` directory.
 
-### Copying logs from Dom0 ###
+### Copying logs from dom0 ###
 
 In order to easily copy/paste the contents of logs from dom0 to the inter-VM clipboard, you can simply:
 
@@ -34,7 +34,7 @@ In order to easily copy/paste the contents of logs from dom0 to the inter-VM cli
 
 You may now paste the log contents to any VM as you normally would (i.e., Ctrl-Shift-V, then Ctrl-V).
 
-### Copy/paste from Dom0 ###
+### Copy/paste from dom0 ###
 
 For data other than logs, there are several options:
 
@@ -49,23 +49,25 @@ For data other than logs, there are several options:
 3.  Write the data you wish to copy into `/var/run/qubes/qubes-clipboard.bin`, then `echo -n dom0 > /var/run/qubes/qubes-clipboard.bin.source`.
     Then use Ctrl-Shift-V to paste the data to the desired VM.
 
-Copying **to** Dom0
+Copying **to** dom0
 -------------------
 
-There should normally be few reasons for the user to want to copy files from VMs to Dom0, as Dom0 only acts as a "thin trusted terminal", and no user applications run there.
-Copying untrusted files to Dom0 is not advised and may compromise the security of your Qubes system.
-Because of this, we do not provide a graphical user interface for it, unlike [copying files between VMs](/doc/copying-files/).
+Copying anything into dom0 is not advised, since doing so can compromise the security of your Qubes system.
+For this reason, there is no simple means of copying anything into dom0, unlike [copying from dom0](#copying-from-dom0) and [copying files between VMs](/doc/copying-files/).
 
-One common use-case for this is if we want to use a desktop wallpaper in Dom0 we have located in one of our AppVMs (e.g. in the 'personal' AppVM where we got the wallpaper from our camera or downloaded it from the Internet).
-While it's a well-justified reason, imagine what would happen if the wallpaper (e.g. a JPEG file) was somehow malformed or malicious and attempted to exploit a hypothetical JPEG parser bug in Dom0 code (e.g. in the Dom0's Xorg/KDE code that parses the wallpaper and displays it).
+There should normally be few reasons for the user to want to copy anything from VMs to dom0, as dom0 only acts as a "thin trusted terminal", and no user applications run there.
+One possible use-case for this is if we want to use a desktop wallpaper in dom0 we have located in one of our AppVMs (e.g. in the 'personal' AppVM where we got the wallpaper from our camera or downloaded it from the Internet).
+While this use-case is understandable, imagine what would happen if the wallpaper (e.g. a JPEG file) was somehow malformed or malicious and attempted to exploit a hypothetical JPEG parser bug in dom0 code (e.g. in the dom0's Xorg/KDE code that parses the wallpaper and displays it).
 
-If you are determined to copy some files to Dom0 anyway, you can use the following method (run this command from Dom0's console):
+If you are determined to copy some files to dom0 anyway, you can use the following method.
+(If you want to copy text, first save it into a text file.)
+Run this command in a dom0 terminal:
 
 ~~~
 qvm-run --pass-io <src-vm> 'cat /path/to/file_in_src_domain' > /path/to/file_name_in_dom0
 ~~~
 
-You can use the same method to copy files from Dom0 to VMs (if, for some reason, you don't want to use `qvm-copy-to-vm`):
+Note that you can use the same method to copy files from dom0 to VMs (if, for some reason, you don't want to use `qvm-copy-to-vm`):
 
 ~~~
 cat /path/to/file_in_dom0 | qvm-run --pass-io <dest-vm> 'cat > /path/to/file_name_in_appvm'