H2: Fix typos

exercises/h2.md

@@ -156,7 +156,7 @@ Bluetooth error messages: lines 7-19. Line 8 is not an error message.
 
 **Analysis - regression test approach (journalctl)**
 
-The following analysis is a part of [the above journalctl issue]((https://github.com/Fincer/linux_server_setup/blob/master/exercises/h2.md#other-error-situations---a-tricky-error-tracked-down))
+The following analysis is a part of [the above journalctl issue](https://github.com/Fincer/linux_server_setup/blob/master/exercises/h2.md#other-error-situations---a-tricky-error-tracked-down)
 
 The problem seem to be widely known among Ubuntu & Arch Linux users, according to a short search in the internet. There is a [launchpad report](https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349) but not a simple answer is given there. There is a suggestion to downgrade bluez package on [Arch Linux forum](https://bbs.archlinux.org/viewtopic.php?id=195886). [AskUbuntu](https://askubuntu.com/) website has many threads for this issue.
 
@@ -170,7 +170,7 @@ Once the problematic commit/commits are known, we can fix the code ourselves and
 
 **Analysis - our bluez package (journalctl)**
 
-The following analysis is a part of [the above journalctl issue]((https://github.com/Fincer/linux_server_setup/blob/master/exercises/h2.md#other-error-situations---a-tricky-error-tracked-down))
+The following analysis is a part of [the above journalctl issue](https://github.com/Fincer/linux_server_setup/blob/master/exercises/h2.md#other-error-situations---a-tricky-error-tracked-down)
 
 In bluez error case, we should check all relevant error messages written by bluetooth daemon to STDERR output. By analysing [BlueZ source code](https://github.com/pauloborges/bluez) ([alternative link](https://git.kernel.org/pub/scm/bluetooth/bluez.git)) we can see that the message present in journalctl log snapshot can be found in source code as well. In more detail, the following source code files (C code):