Merge #96: fix: typo

ff85a1a fix: typo (marathon-gary)

Pull request description:

ACKs for top commit:
  apoelstra:
    utACK ff85a1a
  tcharding:
    ACK ff85a1a

Tree-SHA512: e01339e44556ddf83d64fe2575a5f48009700ec818ca51f089f39188478c9485f906b65645653ce8b42a5e065aeebe9d83ebe54d2cdad07e38b9a5f3d5fad0d1

Author: tcharding

README.md

@@ -14,7 +14,7 @@ This also simplifies cross-compiling the consensus library e.g., for a mobile ap
 `libbitcoinconsensus` refers to code from another library [secp256k1](https://github.com/bitcoin-core/secp256k1).
 A snapshot of that library is also included in the Bitcoin sources, therefore it could be baked into `libbitcoinconsensus`.
 A typical Bitcoin enabled application will however want to access further secp256k1 functions.
-The project [rust-secp256k1](https://github.com/rust-bitcoin/rust-secp256k1) offers a cargo build and Rust bindings, therefore we depend on that instead of compiling the Bitcoin embedded sources into `libbitcoinconsensus`q.
+The project [rust-secp256k1](https://github.com/rust-bitcoin/rust-secp256k1) offers a cargo build and Rust bindings, therefore we depend on that instead of compiling the Bitcoin embedded sources into `libbitcoinconsensus`.
 This introduces a risk, since a difference between the two secp256k1 sources could break consensus with Bitcoin.