From 25a45c582c209df83d26ee931c90851914a67369 Mon Sep 17 00:00:00 2001 From: remiroz <84915012+remiroz@users.noreply.github.com> Date: Fri, 26 May 2023 18:49:56 +0100 Subject: [PATCH] Fix a typo and string in a command (#393) --- site/source/support/faq/faq-troubleshooting.rst | 2 +- site/source/user-manual/ssh.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site/source/support/faq/faq-troubleshooting.rst b/site/source/support/faq/faq-troubleshooting.rst index 5268d98..fe78084 100644 --- a/site/source/support/faq/faq-troubleshooting.rst +++ b/site/source/support/faq/faq-troubleshooting.rst @@ -18,7 +18,7 @@ After plugging into power and your router, you will hear 2 distinct sounds: firs My server is really hot! Is this normal? ----------------------------------------- -On early devices, yes. These cases are actually doing 'double duty' as a heat sync. This means that the metal of the case is actually touching the chips on the circuit board and drawing their heat out and away. This is known as "passive cooling," as no fan (and therefore no noise) is required to cool the system. +On early devices, yes. These cases are actually doing 'double duty' as a heat sink. This means that the metal of the case is actually touching the chips on the circuit board and drawing their heat out and away. This is known as "passive cooling," as no fan (and therefore no noise) is required to cool the system. You can check the chip temperature of your device under "System -> Metrics". diff --git a/site/source/user-manual/ssh.rst b/site/source/user-manual/ssh.rst index 929766f..5d6bfb1 100644 --- a/site/source/user-manual/ssh.rst +++ b/site/source/user-manual/ssh.rst @@ -95,7 +95,7 @@ Connecting via CLI ssh start9@SERVER-HOSTNAME -Replacing ```` with your server's LAN (``.local``) address +Replacing ```` with your server's LAN (``.local``) address .. note:: If you get a scary looking warning that says something like "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" - fear not! This is most likely happening because you have recently reflashed or did an update from pre-v0.3.3, which would cause a change in the key for your device's hostname (e.g. `xxxxxxxx.local`) or IP address (e.g. `192.168.1.x`). The solution is to delete the existing entry from your `known_hosts` file, which is typically located at `~/.ssh/known_hosts`. This will be specified in the warning, along with a helpful line number (in case your file is lengthy).