Docs: Replace "Settings..." with "Preferences/Settings..."

CONTRIBUTING.adoc

@@ -185,7 +185,8 @@ cargo build -Z build-std --release --target x86_64-win7-windows-msvc
 ----
 
 However, linking fails because `windows.lib` can't be opened.
-Probably related to https://www.reddit.com/r/rust/comments/1dikeq6/compiling_for_win7_missing_windows0485lib/[this] and https://github.com/rust-lang/rust/issues/128218#issuecomment-2251864932[this] issue. If -- and only if -- users are genuinely interested in a working Windows 7 build of ReaLearn, I would look into it a bit further.
+Probably related to https://www.reddit.com/r/rust/comments/1dikeq6/compiling_for_win7_missing_windows0485lib/[this] and https://github.com/rust-lang/rust/issues/128218#issuecomment-2251864932[this] issue.
+If -- and only if -- users are genuinely interested in a working Windows 7 build of ReaLearn, I would look into it a bit further.
 
 === Linux
 
@@ -597,7 +598,7 @@ but don't submit yet!
 
 === Windows: ReaLearn DLL doesn't unload
 
-In REAPER for Windows it's possible to enable complete unload of VST plug-ins (Preferences -> Plug-ins -> VST -> Allow complete unload of VST plug-ins).
+In REAPER for Windows it's possible to enable complete unload of VST plug-ins (Options -> Settings/Preferences -> Plug-ins -> VST -> Allow complete unload of VST plug-ins).
 This also affects ReaLearn.
 Removing the last ReaLearn instance should work with and without this flag enabled, it's important to test this.
 

doc/playtime/modules/ROOT/pages/usage/play.adoc

@@ -49,7 +49,7 @@ Maybe you want to play the clip with a lower volume when hitting the key softly
 ====
 Triggering clips via MIDI happens in real-time! As with any other instrument plug-in that you use in REAPER, the latency depends on the block size set in REAPER.
 
-So if you use xref:key-concepts.adoc#clip-start-timing[] xref:user-interface/inspector/clip.adoc#inspector-clip-start-timing-immediately[] and set the block size in REAPER menu:Options[Settings... > Device] low enough (e.g. 256 samples), you will not perceive any delay between pressing the key and hearing the sound.
+So if you use xref:key-concepts.adoc#clip-start-timing[] xref:user-interface/inspector/clip.adoc#inspector-clip-start-timing-immediately[] and set the block size in REAPER menu:Options[Preferences/Settings... > Device] low enough (e.g. 256 samples), you will not perceive any delay between pressing the key and hearing the sound.
 ====
 
 .Is Playtime a sampler?

doc/playtime/modules/ROOT/pages/usage/prepare.adoc

@@ -10,7 +10,7 @@ Playtime runs within REAPER, so at first you need to start REAPER.
 
 If you haven't done it already, you should let REAPER know which audio and MIDI devices you are planning to use with it, because Playtime will use them as well!
 
-. Open the REAPER preferences via menu:Options[Settings...]
+. Open the REAPER preferences via menu:Options[Preferences/Settings...]
 . In the section menu:Audio[Device], configure your audio input and output.
 . In the section menu:Audio[MIDI Inputs], configure your MIDI input devices, such as music keyboards.
 . In the section menu:Audio[MIDI Outputs], configure your MIDI output devices, such as hardware synthesizers.

doc/playtime/modules/ROOT/pages/user-interface/track-area.adoc

@@ -33,7 +33,7 @@ That also means that the track's _input_ FX chain will not have any effect on th
 You can work around this limitation by using *Loopback* channels instead of input FX.
 
 TIP: Selecting *Loopback* channels as audio input doesn't automatically enable them!
-Make sure that the REAPER setting *Virtual loopback audio hardware channels* in menu:Options[Settings... > Audio] is high enough!
+Make sure that the REAPER setting *Virtual loopback audio hardware channels* in menu:Options[Preferences/Settings... > Audio] is high enough!
 
 NOTE: This directly sets the input of the corresponding REAPER track.
 Although technically not necessary for recording because Playtime doesn't use REAPER's track recording facility, it is important for input monitoring.

main/src/infrastructure/proto/initial_events.rs

@@ -58,7 +58,7 @@ pub fn create_initial_instance_updates(
             let swipe_flag = flags & 128 > 0;
             let move_flag = flags & 256 > 0;
             if !wheel_flag || !swipe_flag || !move_flag {
-                let msg = "At least one of the checkboxes in the REAPER preference \"Options → Settings... → General → Advanced UI/system tweaks... → Throttle mouse-events\" is not enabled. This will cause temporary user interface lags in REAPER and Playtime while using the mouse or touchpad in REAPER, e.g. when adjusting the track volume. Enabling all checkboxes will improve your REAPER experience in general, not just when using Playtime!";
+                let msg = "At least one of the checkboxes in the REAPER preference \"Options → Preferences/Settings... → General → Advanced UI/system tweaks... → Throttle mouse-events\" is not enabled. This will cause temporary user interface lags in REAPER and Playtime while using the mouse or touchpad in REAPER, e.g. when adjusting the track volume. Enabling all checkboxes will improve your REAPER experience in general, not just when using Playtime!";
                 warnings.push(Update::warning(
                     Severity::Low,
                     Some(Scope::Playtime),
@@ -88,7 +88,7 @@ pub fn create_initial_instance_updates(
         if let Ok(var) = Reaper::get().get_preference_ref::<i32>("stopprojlen") {
             let stop_at_end = *var;
             if stop_at_end > 0 {
-                let msg = "You have enabled the REAPER preference \"Options → Settings... → Audio → Playback → Stop/repeat playback at end of project\". This prevents Playtime from playing along with your REAPER arrangement if the arrangement is empty or ends prematurely. To ensure smooth operation, we highly recommend disabling this option.";
+                let msg = "You have enabled the REAPER preference \"Options → Preferences/Settings... → Audio → Playback → Stop/repeat playback at end of project\". This prevents Playtime from playing along with your REAPER arrangement if the arrangement is empty or ends prematurely. To ensure smooth operation, we highly recommend disabling this option.";
                 warnings.push(Update::warning(
                     Severity::High,
                     Some(Scope::Playtime),