chore: fix some minor issues in the comments

Signed-off-by: sellskin <mydesk@yeah.net>

Author: sellskin

book/api/websocket.md

@@ -806,7 +806,7 @@ once they are confirmed (the prior epoch has fully rooted).
 | end_time_nanos | ` string` | A UNIX timestamp, in nanoseconds, of when the epoch ended. This is the time the last non-skipped block of the epoch finished replaying locally on this validator, if the validator was online when that happened, otherwise it is null |
 | start_slot | `number` | The first slot (inclusive) in the epoch |
 | end_slot   | `number` | The last slot (inclusive) in the epoch |
-| excluded_stake_lamports | `string` | This number is almost always zero. Firedancer has a limit of 40,200 for the number of staked peer validators it can keep track of. In the unlikely event that this number is exceeded, the lowest staked peers will be forgotten, and their stake will not appear in the below lists. But is is useful to know the total stake in the epoch, so this value represents the leftover/excluded ("poisoned") amount of stake that we do not know which validator it belongs to
+| excluded_stake_lamports | `string` | This number is almost always zero. Firedancer has a limit of 40,200 for the number of staked peer validators it can keep track of. In the unlikely event that this number is exceeded, the lowest staked peers will be forgotten, and their stake will not appear in the below lists. But it is useful to know the total stake in the epoch, so this value represents the leftover/excluded ("poisoned") amount of stake that we do not know which validator it belongs to
 | staked_pubkeys | `string[]` | A list of all of validator identity keys for validators which have are staked in this epoch.  There will be at most 40,200 staked keys, after which lower staked keys will not be included |
 | staked_lamports | `string[]` | A list with the same length as the `staked_pubkeys` field. `stake_lamports[ i ]` is the number of lamports staked on the pubkey `staked_pubkeys[ i ]` as of this epoch
 | leader_slots | `number[]` | An array, one entry per four slots, of which pubkey in the `leader_pubkeys` array is leader for those slots. On `mainnet-beta` this array will always have a length of 108,000, which is the number of slots in an epoch divided by four.  Leader slots are in groups of four because the leader schedule is generated in such a way as to guarantee each leader gets at least four consecutive slots.  For example, to find the pubkey of the leader in slot 1000 of the epoch, it is `staked_pubkeys[ leader_slots[ 1000/4 ] ]` |

src/ballet/bn254/fd_bn254.c

@@ -252,7 +252,7 @@ fd_bn254_pairing_is_one_syscall( uchar       out[32],
       continue;
     }
     ++sz;
-    /* Compute the Miller loop and aggegate into r */
+    /* Compute the Miller loop and aggregate into r */
     if( sz==FD_BN254_PAIRING_BATCH_MAX || i==elements_len-1 ) {
       fd_bn254_fp12_t tmp[1];
       fd_bn254_miller_loop( tmp, p, q, sz );

src/util/tmpl/fd_sort.c

@@ -1193,7 +1193,7 @@ SORT_(fast_para)( fd_tpool_t * tpool, ulong t0, ulong t1,
      where thresh is an empirical minimum amount of sorting work to
      justify starting / stopping a thread.  (As written below, the gamma
      term is more like gamma T^2, which makes the other limit more like
-     the cube root of N ln N but doesn't change the the overall
+     the cube root of N ln N but doesn't change the overall
      conclusion.) */
 
   ulong thresh = (4096UL + sizeof(SORT_KEY_T)-1UL) / sizeof(SORT_KEY_T);