small formatting issues

developer/services/qrexec.md

@@ -109,6 +109,7 @@ Note that if the request is redirected (`target=` parameter), policy action rema
 If no policy rule is matched, the action is denied.
 
 In the target VM, a file in either of the following locations must exist, containing the file name of the program that will be invoked, or being that program itself -- in which case it must have executable permission set (`chmod +x`):
+
   - `/etc/qubes-rpc/RPC_ACTION_NAME` when you make it in the template qube;
   - `/usr/local/etc/qubes-rpc/RPC_ACTION_NAME` for making it only in an app qube.
 

user/advanced-topics/rpc-policy.md

@@ -43,7 +43,7 @@ This is how we create a policy that says: "VMs tagged with 'work' are allowed to
 
 When an operation is initiated with a specific target, e.g. `qvm-copy-to-vm other_work_vm some_file` the policy mechanism looks for a row
 matching `source_work_vm other_work_vm PERMISSION`. In this case, assuming both VMs have the `work` tag, the second row would match, and
-the operation would be `allow`ed without any prompts. When an operation is initiated without a specific target, e.g. `qvm-copy some_file`,
+the operation would be `allow`-ed without any prompts. When an operation is initiated without a specific target, e.g. `qvm-copy some_file`,
 the policy mechanism looks for a row matching `source_work_vm @default PERMISSION`. In this case, the first row indicates that the user
 should be prompted for the destination. The list of destination VMs in the prompt is filtered to only include VMs that are valid as per
 the policy (so in this example, only other work VMs would be listed). If the first row was commented out, the second row would not match