Merge bitcoin#29241: doc: Add missing backtick in developer notes log…

…ging section

c003562 doc: Add missing backtick in developer notes logging section (Fabian Jahr)

Pull request description:

  Newly added logging section from bitcoin#28318 is missing a single backtick. Also fixes some minor punctuation errors in that section.

ACKs for top commit:
  jonatack:
    ACK c003562
  alfonsoromanz:
    ACK c003562

Tree-SHA512: 2f75f9472d212ce7c7ebf3e7404f86b3bd8c695f63e2a7447d7a55bb54dcdb5e3bfd15e8eac5b92efbdcf1216c4e8d699cae0250d021f72b9d1c32a7db91989d

doc/developer-notes.md

@@ -739,25 +739,25 @@ logging messages. They should be used as follows:
   Note that `LogPrint(BCLog::CATEGORY, fmt, params...)` is a deprecated
   alias for `LogDebug`.
 
-- `LogInfo(fmt, params...)` should only be used rarely, eg for startup
+- `LogInfo(fmt, params...)` should only be used rarely, e.g. for startup
   messages or for infrequent and important events such as a new block tip
   being found or a new outbound connection being made. These log messages
-  are unconditional so care must be taken that they can't be used by an
+  are unconditional, so care must be taken that they can't be used by an
   attacker to fill up storage. Note that `LogPrintf(fmt, params...)` is
   a deprecated alias for `LogInfo`.
 
 - `LogError(fmt, params...)` should be used in place of `LogInfo` for
   severe problems that require the node (or a subsystem) to shut down
-  entirely (eg, insufficient storage space).
+  entirely (e.g., insufficient storage space).
 
 - `LogWarning(fmt, params...)` should be used in place of `LogInfo` for
   severe problems that the node admin should address, but are not
-  severe enough to warrant shutting down the node (eg, system time
+  severe enough to warrant shutting down the node (e.g., system time
   appears to be wrong, unknown soft fork appears to have activated).
 
-- `LogTrace(BCLog::CATEGORY, fmt, params...) should be used in place of
+- `LogTrace(BCLog::CATEGORY, fmt, params...)` should be used in place of
   `LogDebug` for log messages that would be unusable on a production
-  system, eg due to being too noisy in normal use, or too resource
+  system, e.g. due to being too noisy in normal use, or too resource
   intensive to process. These will be logged if the startup
   options `-debug=category -loglevel=category:trace` or `-debug=1
   -loglevel=trace` are selected.