code review comments

Co-authored-by: thephez <[email protected]>
Co-authored-by: UdjinM6 <[email protected]>

Author: 3 people

doc/release-notes.md

@@ -35,31 +35,31 @@ is now packaged in a ZIP archive. The macOS distribution is once again notarized
 BIP324 / v2 P2P Protocol
 ------------------------
 
-Version 2 of the Dash P2P protocol / BIP324, which enables encryption of the p2p protocol
+Version 2 of the Dash P2P protocol / BIP324, which enables encryption of the p2p protocol,
 has been enabled by default in this version. This was initially introduced in Dash Core
-v22.0.0 as an experimental feature, and has been now enabled by default. This change is
-backwards compatible, and connections to peers which do not support the v2 protocol will
+v22.0.0 as an experimental feature and has now been enabled by default. This change is
+backward compatible, and connections to peers which do not support the v2 protocol will
 revert to using the v1 protocol.
 
 Network Changes
 ---------------
 System ports, or ports that are lower than 1024 are now considered to be "bad" ports.
 As a result, other peers will avoid connecting to nodes that are listening on these ports.
-This change is to prevent potential DDoS attacks on services that are running on these ports.
+This change is to prevent potential DDoS attacks against services running on these ports.
 A number of other ports commonly used for authenticated services are also considered "bad" ports.
 You can view [the list of bad ports here](doc/p2p-bad-ports.md).
 
 Tests
 -----
 
-- Command line arguments -dip8params, -bip147height are removed in favour of -testactivationheight. (dash#6325)
-- A number of hard forks now activate earlier on regtest. 
+- Command line arguments `-dip8params`, `-bip147height` are removed in favour of `-testactivationheight`. (dash#6325)
+- Several hard forks now activate earlier on regtest.
 
 ## New RPCs
 
 - **`getislocks`**
     - Retrieves the InstantSend lock data for the given transaction IDs (txids).
-      Returns the lock information in both human-friendly JSON format and binary hex-encoded zmq-compatible format.
+      Returns the lock information in both a human-friendly JSON format and a binary hex-encoded zmq-compatible format.
 
 Updated RPCs
 ------------
@@ -70,7 +70,7 @@ Updated RPCs
   are deprecated and will be removed in the next major version (use
   `-deprecated=fees` if needed in this version). The same fee fields can be accessed
   through the `fees` object in the result. WARNING: deprecated
-  fields `ancestorfees` and `descendantfees` are denominated in sats, whereas all
+  fields `ancestorfees` and `descendantfees` are denominated in duffs, whereas all
   fields in the `fees` object are denominated in DASH.
 - **`getbestchainlock` Changes**
     - A new hex field has been added to the getbestchainlock RPC, which returns the ChainLock information in zmq-compatible, hex-encoded binary format.
@@ -81,8 +81,8 @@ Updated RPCs
 GUI changes
 -----------
 
-- UTXOs which are locked via the GUI are now stored persistently in the
-  wallet database, so are not lost on node shutdown or crash.
+- UTXOs locked via the GUI are now stored persistently in the
+  wallet database and are not lost on node shutdown or crash.
 - Improved GUI responsiveness for large wallets. (dash#6457)
 
 # v22.1.0 Change log
@@ -97,6 +97,7 @@ Thanks to everyone who directly contributed to this release:
 - Konstantin Akimov
 - PastaPastaPasta
 - UdjinM6
+- Vijaydasmp
 
 As well as everyone that submitted issues, reviewed pull requests and helped
 debug the release candidates.