diff --git a/hsc-options-explained.md b/hsc-options-explained.md
index 0f2ba15..575d3b8 100644
--- a/hsc-options-explained.md
+++ b/hsc-options-explained.md
@@ -33,7 +33,15 @@ The `ac_algo` parameter changes the chain's mining algorithm from the default eq
 ### Different Equihash
 If you want to enable a different form of the EquiHash algorithm, then set `-ac_algo=equihash -ac_nk=N,K` where N and K would be your specified values.
 
-As an example, BEAM uses Equihash (150,5), so it would include `-ac_algo=equihash -ac_nk=150,5`.
+[Valid (N,K)](https://git.hush.is/hush/hush3/src/branch/master/src/hush_utils.h#L1727) choices are:
+* (200,9) (the default, used by HUSH and ZEC)
+* (210,9)
+* (48,5)
+* (96,5)
+* (144,5)
+* (150,5)
+
+As an example, BEAM uses Equihash (150,5), so it would include `-ac_algo=equihash -ac_nk=150,5` in its parameters.
 
 ### Use randomX algorithm
 To enable randomX algorithm, set `-ac_algo=randomx`.
@@ -158,6 +166,10 @@ After Using `ac_ccactivate`
 
 In this example, CryptoCondition will be available at blockheight `140`. All nodes, include the notary nodes, must relaunch the daemon with the new parameters before blockheight `140`.
 
+## ac_ccactivateht
+
+Set the height for enabling cryptoconditions transactions. CC transactions before this height will be ignored. This can be used to enable CC's on a chain which was launched without having CC's enabled at the time of it's genesis block.
+
 ## ac_ccenable
 
 The `ac_ccenable` parameter restricts the Smart Chain so that only indicated CryptoCondition modules can be enabled. `ac_ccenable` requires ac_cc to be active.
@@ -572,14 +584,6 @@ Found these other parameters in hush_utils.h not present in other docs...
 
 It's in code [here](https://git.hush.is/hush/hush3/src/branch/master/src/cc/pegs.cpp#L26). I first found `-ac_import` which led me to peg... and `-ac_pegsccparams`
 
-## misc
-
-* -ac_ccactivateht
-* -ac_beam
-* -ac_coda
-* -ac_mineropret
-* -ac_overwinter
-
 ## Reference
 
 To learn more about the origin of CryptoConditions, please refer to this [IETF documentation here](https://datatracker.ietf.org/doc/html/draft-thomas-crypto-conditions-03).