Merge pull request #530 from emmanuel-ferdman/master

Update `KnownIssues.md` reference

documentation/TimeSystemExplained.md

@@ -16,7 +16,7 @@ The Polar devices keeps track of the time. The device time is used by the device
     - H10, H9: resets back to default time when the sensor shutdowns. Shutdown of sensor happen within in a minute, if sensor is detach from the strap and it has no bluetooth connection. 
     - OH1, Verity Sense: default time is set only when the device runs out of battery, which might take several weeks when the device is powered off.
 
-When a Polar device completely lose track of time, it's time is reset to a default value which might be different for any product. It is usally good practice to get the time of the device regularly to detect this possible scenario. 
+When a Polar device completely lose track of time, it's time is reset to a default value which might be different for any product. It is usually good practice to get the time of the device regularly to detect this possible scenario. 
 
 ***Timestamp*** 
 - the timestamp is the time given for each sample taken by the Polar device. 
@@ -35,4 +35,4 @@ When a Polar device completely lose track of time, it's time is reset to a defau
 
 **Some considerations:**
 - Note 1: one may use the epoch time to human readable time converters in the code. The conversion algorithms are usually based on the unix epoch of 1970-01-01T00:00:00Z. If that is the case then one shall add the offset between 1970-01-01T00:00:00Z and 2000-01-01T00:00:00Z to timestamp before passing the timestamp to converter. Offset in nanoseconds is 946684800000000000 
-- there are known issues related to sensor time, please see them [known issues](https://github.com/polarofficial/polar-ble-sdk/blob/master/technical_documentation/KnownIssues.md) 
+- there are known issues related to sensor time, please see them [known issues](https://github.com/polarofficial/polar-ble-sdk/blob/master/documentation/KnownIssues.md)