Documentation improvements

docs/build/setup.md

@@ -35,11 +35,11 @@ The configuration UI of the device should open nowt that looks like this:
   The number of seconde the device will open the local hotspot when powering up before it connects to your home WiFi. Set this to a low value, e.g. 5 seconds.
 
 - Client-ID:  
-  Client-ID of the Azure App that is used to connect to Teams. You can use the Generic-ID 3837bbf0-30fb-47ad-bce8-f460ba9880c3 or setup your own Azure App. The Generic-ID should work fine in most cases as it's a multi-tenant app I supply.
+  Client-ID of the Azure App that is used to connect to Teams. You can use the Generic-ID 3837bbf0-30fb-47ad-bce8-f460ba9880c3 or setup your own Azure App. The Generic-ID should work fine in most cases. It's a multi-tenant app I registered that you can use instead registering your own Azure app (what's also possible).
 - Tenant hostname / ID:  
   Hostname of your tenant, e.g. contoso.onmicrosoft.com. You can also use the tenant GUID.
 - Presence polling interval (sec):  
-  Intervall to poll for new presence information. Don't set this too low, you may stress the Azure infrastructure too much, if you set it too low, and get throttled. 90 seconds or more may be a good value.
+  Intervall to poll for new presence information. Don't set this too low, you may stress the Azure infrastructure too much, and get throttled. 90 seconds or more may be a good value.
 - Number of LEDs:  
   The number of LEDs in neopixel ring / strip.
 
@@ -86,9 +86,8 @@ After login is completed you should may see this dialog:
 
 It asks you to consent that the Azure App, that the presence device uses in the background, is allowed to access your profile and presence data (and nothing else).
 
-If you have some admin role in Azure AD you maybe see the "Consent in the name of your organization" checkbox. If you tick this, other users in your tenant don't need to consent on their own.
+If you have some admin role in Azure AD you may see the "Consent in the name of your organization" checkbox. If you tick this, other users in your tenant don't need to consent on their own.
 
-Click "Accept" and you should be done. The access tokens (only the tokens, no personal credentials) are now stored on the device. The token is refreshed automatically if needed in the future.
+Click "Accept" and you should be done. The access tokens (only the tokens, no personal credentials) are now stored on the device. The token is refreshed automatically, if needed, in the future.
 
 The presence device should now get presence information and light up in the color of your presence.
-

docs/buy.md

@@ -49,7 +49,7 @@ Neopixel variants:
 
 You can package the parts in numerous ways and maybe you have the perfect case already lying around. If not, you can print a case if you have access to a 3D printer.
 
-The design can be found on thingyverse: https://www.thingiverse.com/thing:4296998
+The design can be found on thingiverse: https://www.thingiverse.com/thing:4296998
 This is a [existing design](https://www.thingiverse.com/thing:4060603) from [Plankto](https://www.thingiverse.com/Plankto/about), I modified it to fit the neopixel ring and a ESP32.
 
 ![Neopixel variants](https://github.com/toblum/ESPTeamsPresence/raw/master/docs/pics/case_printanimation.gif)
@@ -63,4 +63,4 @@ You can get these really cheap:
 - https://www.amazon.de/Aukru-20cm-female-female-Steckbr%C3%BCcken-Drahtbr%C3%BCcken/dp/B00OL6JZ3C
 - https://de.aliexpress.com/item/32987024879.html
 
-And you need a simple Micro-USB cable to flash the ESP32 and power it later. You definitely have one lying around somewhere. 
+And you also need a simple Micro-USB cable to flash the ESP32 and power it later. You definitely have one lying around somewhere.