diff --git a/docs/FAQ.md b/docs/FAQ.md
index d1b6158b..57469da4 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -86,19 +86,21 @@
 * **The official PowerShell documentation can be found here:** https://docs.microsoft.com/en-us/powershell/
 </details>
 
-<details><summary>What about security?</summary>
+<details><summary>What about PowerShell security?</summary>
 
-1. **Execute scripts only that you trust (and/or where you have checked the code before)!**
+1. **Do not execute scripts from untrusted sources. We also recommend to check the code before use.**
 2. **Prefer SSH Remoting instead of PowerShell Remoting**
 3. **More recommendations by NSA and cyber security centers in the U.S. (CISA), New Zealand (NZ NCSC), and the U.K. (NCSC-UK) can be found here:** https://media.defense.gov/2022/Jun/22/2003021689/-1/-1/1/CSI_KEEPING_POWERSHELL_SECURITY_MEASURES_TO_USE_AND_EMBRACE_20220622.PDF
  </details>
 
  <details><summary>How to get the best PowerShell experience?</summary>
 
-1. **On Windows: install and use *Windows Terminal* with 50% transparency, font 'Fira Code' and no PowerShell banner message.**
-2. **Install and use *Visual Studio Code* with plugin 'PowerShell' to edit PowerShell scripts.**
-3. **Install the *Mega Collection of PowerShell scripts* and set the PATH environment variable to it.**
-4. **Use an own PowerShell profile, e.g. execute: './update-powershell-profile.ps1'**
+1. **Install *PowerShell* on all your Linux/Mac OS/Windows machines.**
+2. **Configure *PowerShell* as default shell on all your machines.**
+3. **On Windows: install and use *Windows Terminal* with 50% transparency, font 'Fira Code' and no PowerShell banner message.**
+4. **Install and use *Visual Studio Code* with plugin 'PowerShell' to edit PowerShell scripts.**
+5. **Install the *Mega Collection of PowerShell scripts* and set the PATH environment variable to it.**
+6. **Use an own PowerShell profile, e.g. execute: './update-powershell-profile.ps1'**
 </details>