diff --git a/dependencies.md b/dependencies.md
index 9f89b57..9fd25c9 100644
--- a/dependencies.md
+++ b/dependencies.md
@@ -7,7 +7,7 @@ categories: dependencies
 ---
 
 `jabit-core` contains the Bitmessage context and all entities that will be used by the other modules.
-Whatever you do, you'll need this.
+Whatever you do, you'll always need this.
 
 `jabit-networking` manages connections to the Bitmessage network. This is probably the most complicated
 part of the Jabit project. TODO
@@ -18,12 +18,14 @@ requests) but if you want to use some NoSQL database or a very restricted one (a
 want to create your own implementation.
 
 `jabit-cryptography-bouncy` impmlements everything related to encryption, cryptographic hashes and
-secure random numbers. As the name suggests, it uses the [Bouncycastle](https://www.bouncycastle.org/)
-library.
+secure random numbers. As the name suggests, it uses the [Bouncycastle][bouncycastle] library.
 
-`jabit-cryptography-spongy` is basically a copy of the spongy one, but using
-[Spongycastle](https://rtyley.github.io/spongycastle/) instead.
+`jabit-cryptography-spongy` is basically a copy of the spongy one, but using [Spongycastle][spongycastle]
+instead. Go there and look at the first section "why?" for the messed up reason this module exists.
 
 `jabit-wif` lets you import from and export to the Wallet Import Format, which is used by PyBitmessage to store its identities.
 
-`jabit-extensions` you won't usually need, it contains a few helper classes for if you want to build protocol extensions.
\ No newline at end of file
+`jabit-extensions` you won't usually need, it contains a few helper classes for if you want to build protocol extensions.
+
+[bouncycastle]: https://www.bouncycastle.org/
+[spongycastle]: https://rtyley.github.io/spongycastle/
\ No newline at end of file