Update the docs to eliminate the mention of the Spoken Interface setting until re-added.

src/tangara/tts/README.md

@@ -15,10 +15,12 @@ The code is structured in three pieces:
 
 ## End-user Configuration
 
-Text-to-speech can be enabled under the Display settings on Tangara, by
+Text-to-speech will automatically be enabled if you have loaded TTS phrases
-enabling the _"Spoken Interface"_ setting. Please note that this will not be
+onto the SD card, under `/.tangara-tts/`. These samples must be formatted
-a user-visible change unless TTS phrases are loaded onto the SD card under
+and named as per the instructions below.
-`/.tangara-tts/`.
+
+To disable TTS, rename or delete the `/.tangara-tts/` directory on your SD
+card.
 
 ## Supported Codecs
 
@@ -35,13 +37,13 @@ files, with a `.wav` extension, named as the hexadecimal version of the
 
 For example, `Settings` hashes to `1e3e816187453bf8`. If you recorded a
 short sample as a 48kHz (mono or stereo) WAV file, and stored it on the SD
-card as `/.tangara-tts/1e3e816187453bf8.wav`, it would be played back when the
+card as `/.tangara-tts/1e3e816187453bf8.wav`, it would be played back when
-settings icon is highlighted.
+the settings icon is highlighted.
 
 ## Finding the KOMIHASH of UI strings
 
-If you connect to your Tangara via the serial console, the `provider` module
+If you connect to your Tangara via the serial console, the TTS provider
-logs a `WARN`ing each time it cannot find a TTS sample. You can enable these
+logs a `WARN`ing each time it cannot find a TTS sample. You can enable
-log messages on the console by using the command `loglevel warn`, and then
+these log messages on the console by using the command `loglevel warn`,
-manipulating the click wheel to move through the UI to discover other missing
+and then manipulating the click wheel to move through the UI to discover
-TTS samples.
+other missing TTS samples.