lints

content/docs/crypto/constant_time_tool/timecop.md

@@ -98,7 +98,6 @@ Once the program uses the uninitialized values for either:
 - *Conditional jump*: Altering the execution trace
 - *Move*: Altering the memory access patterns
 
-
 Valgrind will issue a report.
 
 Consider the following example of the propagation of uninitialized values:
@@ -212,7 +211,7 @@ For a more informative GDB experience, consider using [pwndbg](https://github.co
 To start debugging run:
 
 ```bash
-$ valgrind --vgdb=yes --vgdb-error=0 ./<binary>
+valgrind --vgdb=yes --vgdb-error=0 ./<binary>
 ```
 
 which tells Valgrind to start in GDB mode and break before executing the binary.

content/docs/crypto/wycheproof/_index.md

@@ -38,7 +38,6 @@ The vectors are organized in two main folders:
 
 with plans to merge them in the future.
 
-
 While both folders contain similar test vector files, `testvectors_v1` includes more detailed information.
 The test vectors, stored in JSON-encoded files, can be used as input in a testing harness to verify the correctness of a cryptographic implementation by comparing the actual output to the expected output specified in the test vector.
 To use the test vectors provided by Wycheproof, integrate them into the testing procedures of the cryptographic library you want to test by writing a testing harness.
@@ -145,7 +144,6 @@ This greatly benefits developers as they only need to write the testing harness
 We recommend adding Wycheproof as a submodule to the GitHub repository.
 If this is not possible, we also provide a simple script fetching specific test vectors from the Wycheproof repository.
 
-
 ### Git Submodule
 
 Adding Wycheproof as a git submodule will ensure that you can automatically use new test vectors added to the construction under test.