diff --git a/Console-Logs.md b/Console-Logs.md
index 73d984b..6e20c7c 100644
--- a/Console-Logs.md
+++ b/Console-Logs.md
@@ -141,7 +141,6 @@ Line 4, only displayed in single coin pools
 
 * network hashrate estimate is calculated from network difficulty and the number of blocks found during
  the mining session.
-* observed network block TTF calculated from the number of blocks found during the session.
 
 ### Getwork new block, work report
 
@@ -165,16 +164,19 @@ therefore considered correct.
 
 
 The main purpose of the share submitted report is to timestamp the event to measure latency. It also contains
-info to help tracking.
+info to help tracking. The diff, block, and job, as well as the share counter are also reported in the share
+result log
 
 * submit count is a simple counter that is incremented every time a share is submitted. It should always
 match up with a share result counter.
 
-* The difficulty of the submitted share, should be <= target diff to be accepted, otherwise it will be rejected
-as a low difficulty share. Low difficulty shares are caused by using the wrong algorithm or wrong pamameters,
-a pool misconfiguration or a bug in cpuminer-opt. A bug is more likely with new code.
+* The difficulty of the submitted share, should be less than or equal to the target difficulty
+to be accepted, otherwise it will be rejected as a low difficulty share. Low difficulty shares are usually
+discarded by the miner and not submitted. Submitting a low difficulty share is caused by using the wrong
+algorithm or wrong pamameters, a pool misconfiguration or a bug in cpuminer-opt. A bug is more likely with
+new algorithms or recently changed code.
 
-* The current block, also known as height.
+* The current block being mined, also known as height.
  
 * The job id, stratum only, useful to troubleshoot stale shares.
 
@@ -212,7 +214,8 @@ or a stratum mismatch due to a pool misconfiguration or software bug. When troub
 shares the share difficulty and the target difficulty from the new block log are useful information.
 
 * The submit time in seconds since the last share. Determines share rate (shares/minute) which combined with
-the stratum difficulty determines the effective hash rate. This is how pools calculate hash rate.
+the stratum difficulty determines the effective hash rate. The share rate is used by pools to calculate
+hash rate.
 
 * (Latency ms) Time in milliseconds from share submission to reply, including transmission time and processing
 at either end.