From b44f952b4407a886347d9bba3b1ddab58bfd2050 Mon Sep 17 00:00:00 2001 From: mickael e Date: Mon, 8 Jul 2019 16:58:28 -0400 Subject: [PATCH] Address doc review comments --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6f915d7d..d4b7eeb2 100644 --- a/README.md +++ b/README.md @@ -184,7 +184,7 @@ The development plan is to provide functionality in the *SecureDrop Client* that ##### Automated export flows -The `sd-export-usb` disposable VM handles exports to USB devices through `qvm-open-in-vm`. USB device IDs are configured in `config.json`. The automated export flows make use of the `qvm-usb --persistent` feature. This means that the persistent USB device must be available for `sd-export-usb` to start. In other words, a USB memory stick or a printer must be connected **prior** to the the `qvm-open-in-vm sd-export-usb` call is made. +The `sd-export-usb` disposable VM handles exports to USB devices through `qvm-open-in-vm`. USB device IDs are configured in `config.json`. The automated export flows make use of the `qvm-usb --persistent` feature. This means that the persistent USB device must be available for `sd-export-usb` to start. In other words, a USB memory stick or a printer must be connected **before** the call to `qvm-open-in-vm sd-export-usb ` is made. ###### Automated encrypted USB export flow (Work in progress, client integration TBD)