Recent reports from some users have suggested that the current UI/UX pertaining to folder-removal can be confusing for at least two reasons:

1. Despite the informational text in the removal-confirmation dialog (which explicitly states that "[r]emoved folders will remain on your computer but Gridsync will no longer synchronize their contents with "), some users have expected "remove" to also entail local deletion and are thus surprised when the act of "removing" a folder in the UI leaves a copy of that folder locally.

2. The "Allow this folder to be restored later with my Recovery Key" checkbox essentially prompts users to consider whether they want to unlink a folder's capabilities from their "rootcap" but this, too, can be confusing: it dilutes the originally intend functionality of the Recovery Key (i.e., of giving users the ability restore a grid-connection and previously-active folders in the event that something goes wrong) by, instead, framing it to work more akin to a "recycle bin" (whereby keeping the checkbox checked will simply convert it to a "remotely stored" folder from which it can be re-downloaded later, while unchecking it will "really" "delete" it). Previously, users have questioned why they "need to delete a folder twice", not realizing that the state of the checkbox is what determines this.

Accordingly, these issues should be ameliorated as follows:

1. The "remove" option should instead be re-framed as "stop syncing" (or similar) in order more clearly convey the underlying functionality.

2. The "allow this folder to be restored..." option should be clarified but switched to unchecked by default such that clicking "yes" will unlink the capabilities from the user's rootcap while still allowing users to keep a "remotely stored" copy should they wish.