Fix CLI flags

book/src/help_bn.md

@@ -9,11 +9,11 @@ USAGE:
     lighthouse beacon_node [FLAGS] [OPTIONS]
 
 FLAGS:
-        --allow-insecure-genesis-sync          Enable syncing from genesis. This is insecure after Capella due to long-
-                                               range attacks. This should only be used for testing. DO NOT use on
+        --allow-insecure-genesis-sync          Enable syncing from genesis, which is generally insecure and incompatible
+                                               with data availability checks. Checkpoint syncing is the preferred method
+                                               for syncing a node. Only use this flag when testing. DO NOT use on
                                                mainnet!
-        --always-prefer-builder-payload        If set, the beacon node always uses the payload from the builder instead
-                                               of the local payload.
+        --always-prefer-builder-payload        This flag is deprecated and has no effect.
         --always-prepare-payload               Send payload attributes with every fork choice update. This is intended
                                                for use by block builders, relays and developers. You should set a fee
                                                recipient on this BN and also consider adjusting the --prepare-payload-
@@ -178,12 +178,8 @@ OPTIONS:
             `SLOTS_PER_EPOCH`, it will NOT query any connected builders, and will use the local execution engine for
             payload construction. [default: 8]
         --builder-profit-threshold <WEI_VALUE>
-            The minimum reward in wei provided to the proposer by a block builder for an external payload to be
-            considered for inclusion in a proposal. If this threshold is not met, the local EE's payload will be used.
-            This is currently *NOT* in comparison to the value of the local EE's payload. It simply checks whether the
-            total proposer reward from an external payload is equal to or greater than this value. In the future, a
-            comparison to a local payload is likely to be added. Example: Use 250000000000000000 to set the threshold to
-            0.25 ETH. [default: 0]
+            This flag is deprecated and has no effect.
+
         --builder-user-agent <STRING>
             The HTTP user agent to send alongside requests to the builder URL. The default is Lighthouse's version
             string.
@@ -316,14 +312,6 @@ OPTIONS:
         --http-tls-key <http-tls-key>
             The path of the private key to be used when serving the HTTP API server over TLS. Must not be password-
             protected.
-        --ignore-builder-override-suggestion-threshold <PERCENTAGE>
-            When the EE advises Lighthouse to ignore the builder payload, this flag specifies a percentage threshold for
-            the difference between the reward from the builder payload and the local EE's payload. This threshold must
-            be met for Lighthouse to consider ignoring the EE's suggestion. If the reward from the builder's payload
-            doesn't exceed the local payload by at least this percentage, the local payload will be used. The conditions
-            under which the EE may make this suggestion depend on the EE's implementation, with the primary intent being
-            to safeguard against potential censorship attacks from builders. Setting this flag to 0 will cause
-            Lighthouse to always ignore the EE's suggestion. Default: 10.0 (equivalent to 10%). [default: 10.0]
         --invalid-gossip-verified-blocks-path <PATH>
             If a block succeeds gossip validation whilst failing full validation, store the block SSZ as a file at this
             path. This feature is only recommended for developers. This directory is not pruned, users should be careful