From 0cb21c89c36fee89dbbe2d9a64e9510fe1624deb Mon Sep 17 00:00:00 2001
From: Philippe Teuwen <phil@teuwen.org>
Date: Sat, 2 May 2020 23:11:49 +0200
Subject: [PATCH] doc

---
 armsrc/Standalone/readme.md |  2 +-
 doc/bt_manual_v10.md        | 13 +++++++++----
 2 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/armsrc/Standalone/readme.md b/armsrc/Standalone/readme.md
index d46943778..3775d848c 100644
--- a/armsrc/Standalone/readme.md
+++ b/armsrc/Standalone/readme.md
@@ -131,7 +131,7 @@ Remember only one can be selected at a time for now.
 
 The final steps is to 
 - force recompilation of all code.  ```make clean```
-- compile ```make -j8```
+- compile ```make -j```
 - flash your device
 - connect to your device
 - press button long time to trigger ledshow and enter your new standalone mode
diff --git a/doc/bt_manual_v10.md b/doc/bt_manual_v10.md
index 42f8c04b9..8a08fcdcd 100644
--- a/doc/bt_manual_v10.md
+++ b/doc/bt_manual_v10.md
@@ -55,7 +55,7 @@ https://github.com/RfidResearchGroup/proxmark3
 To compile the client and firmware with FPC support, the easiest way is to 
 
 1. Copy the sample file:  `Makefile.platform.sample`  ⇒   `Makefile.platform`
-    * `mv Makefile.platform.sample Makefile.platform`
+    * `cp Makefile.platform.sample Makefile.platform`
 2. Edit `Makefile.platform`,  uncomment the line `#PLATFORM_EXTRAS=BTADDON` by removing the `#`
 3. Recompile the project:
    * `make clean; make -j`
@@ -113,10 +113,15 @@ http://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp
 
 This requires to have compiled the client with Bluetooth support.
 
+Be sure your user has permissions to use Bluetooth
+
+  * On most distributions, you've to be part of group `bluetooth`: `sudo adduser $USER bluetooth` then log out and log in
+  * else, run the following commands as root : `sudo ...`
+
 1. Find the MAC address of the Bluetooth add-on, named PM3_RDV4.0.
 
 ```sh
-sudo hcitool scan
+hcitool scan
 Scanning ...
   aa:bb:cc:dd:ee:ff PM3_RDV4.0
 ```
@@ -136,7 +141,7 @@ restart it again after pairing.
 If your OS doesn't prompt you for pairing, you can do it in command line, e.g. (again, replace with your addon MAC address):
 
 ```sh
-sudo bluetoothctl
+bluetoothctl
 [bluetooth]# pairable on
 [bluetooth]# scan on
 Discovery started
@@ -178,7 +183,7 @@ rfcomm is a deprecated tool which might be unavailable in your Linux distributio
 1. Find the MAC address of the Bluetooth add-on, named PM3_RDV4.0.
 
 ```sh
-sudo hcitool scan
+hcitool scan
 Scanning ...
   aa:bb:cc:dd:ee:ff PM3_RDV4.0
 ```