diff --git a/FAQ.md b/FAQ.md
index dd6bb07..5cb8a2c 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -6,7 +6,7 @@ Every invocation of `signal-cli ...` starts a Java Virtual Machine instance. Thi
 
 To avoid it, signal-cli can be started as a daemon, with subsequent commands sent to it through DBus. See [using `dbus-send`](https://github.com/AsamK/signal-cli/wiki/DBus-service#user-content-send-using-dbus-send).
 
-There is a also an experimental native library build using GraalVM that avoids JVM startup. See [GraalVM section in README](https://github.com/AsamK/signal-cli/blob/master/README.md#user-content-building-a-native-binary-with-graalvm-experimental)
+There is a also an experimental native library build using GraalVM that avoids JVM startup. See [GraalVM section in README](https://github.com/AsamK/signal-cli/blob/master/README.md#user-content-building-a-native-binary-with-graalvm-experimental).
 
 
 #### System entropy
@@ -15,7 +15,7 @@ Some signal-cli's operations require that enough system entropy / randomness is
 
 Available entropy can be monitored with
 
-	watch cat /proc/sys/kernel/random/entropy_avail 
+	watch cat /proc/sys/kernel/random/entropy_avail
 
 If it is hitting zero during `signal-cli ...` execution, signal-cli will block until enough entropy is available.