Only suggest using symlinks with sandboxed plugins

Now that I think about it it's pretty obvious why symlinks only work
with hosts that support plugin sandboxing (since your OS will never load
two instaces of an identical .so file into the same process). Still, I
find using symlinks in hosts that do sandbox their plugins to be very
user friendly, especially while developing.

CHANGELOG.md

@@ -6,6 +6,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic
 Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+### Changed
+
+- Changed installation recommendations to only install using symlinks with hosts
+  that support individually sandboxed plugins.
+
 ## [1.1.0] - 2020-05-07
 
 ### Added
@@ -37,8 +44,8 @@ Versioning](https://semver.org/spec/v2.0.0.html).
 - Fixed plugins failing to load on certain versions of _Ubuntu_ because of
   paths starting with two forward slashes.
 - Redirect the output from the Wine host process earlier in the startup process.
-  Otherwise errors printed startup won't be visible, making it very hard to
-  diagnose problems.
+  Otherwise errors printed during startup won't be visible, making it very hard
+  to diagnose problems.
 
 ## [1.0.0] - 2020-05-03