Apply suggestions from code review

Co-authored-by: Matevž Jekovec <[email protected]>

docs/dapp/sapphire/security.md

@@ -36,8 +36,8 @@ You can also trace a particular transaction, once you know its hash.
 npx hardhat trace --hash 0xTransactionHash
 ```
 
-For both [gas] usage and confidentiality purposes, we recommend using
-non-unique data size. E.g. 64-byte value will still be distinct from a
+For both [gas] usage and confidentiality purposes, we **recommend using
+non-unique data size**. E.g. 64-byte value will still be distinct from a
 128-byte value.
 
 :::caution Inference based on access patterns
@@ -50,7 +50,7 @@ transaction.
 ## Order of Operations
 
 When handling errors, gas usage patterns not only can reveal the code path
-taken, but sometimes the balance of a user as well (in the case of a diligent
+taken, **but sometimes the balance of a user as well** (in the case of a diligent
 attacker using binary search).
 
 ```solidity
@@ -79,8 +79,8 @@ function transferFrom(address who, address to, uint amount)
 ## Gas Padding
 
 To prevent leaking information about a particular transaction, Sapphire
-provides a [precompile] for dApp developers to pad the amount of gas used
-in a transaction.
+provides a [precompile] for dApp developers to **pad the amount of gas used
+in a transaction**.
 
 ```solidity
 contract GasExample {