fix typos

book/src/builders.md

@@ -40,7 +40,7 @@ With the `--prefer-builder-proposals` flag, the validator client will always pre
 ```
 lighthouse vc --builder-boost-factor <INTEGER>
 ```
-With the `--builder-boost-factor` flag, a percentage multiplier to apply to the builder's payload value when choosing between a
+With the `--builder-boost-factor` flag, a percentage multiplier is applied to the builder's payload value when choosing between a
 builder payload header and payload from the paired execution node.
 
 In order to configure whether a validator queries for blinded blocks check out [this section.](#validator-client-configuration)
@@ -58,10 +58,9 @@ relays, run one of the following services and configure lighthouse to use it wit
 In the validator client you can configure gas limit and fee recipient on a per-validator basis. If no gas limit is
 configured, Lighthouse will use a default gas limit of 30,000,000, which is the current default value used in execution
 engines.  You can also enable or disable use of external builders on a per-validator basis rather than using
-`--builder-proposals` (enables external builders for all validators), `--builder-boost-factor` (increase/decrease preference for builder payloads)
-or `--prefer-builder-proposals` (always prefer builder payloads). In order to manage these configurations
-per-validator, you can either make updates to the `validator_definitions.yml` file or you can use the HTTP requests
-described below.
+`--builder-proposals`, `--builder-boost-factor` or `--prefer-builder-proposals`, which apply builder related preferences fpr all validators.
+In order to manage these configurations per-validator, you can either make updates to the `validator_definitions.yml` file
+or you can use the HTTP requests described below.
 
 Both the gas limit and fee recipient will be passed along as suggestions to connected builders. If there is a discrepancy
 in either, it will *not* keep you from proposing a block with the builder. This is because the bounds on gas limit are

book/src/help_vc.md

@@ -57,7 +57,7 @@ FLAGS:
             be used with caution. For Windows users, the log file permissions will be inherited from the parent folder.
         --metrics                                Enable the Prometheus metrics HTTP server. Disabled by default.
         --prefer-builder-proposals
-            If this flag is set, Lighthouse  will always prefer blocks constructed by builders, regardless of builder payload value.
+            If this flag is set, Lighthouse will always prefer blocks constructed by builders, regardless of builder payload value.
         --produce-block-v3
             Enable block production via the block v3 endpoint for this validator client. This should only be enabled
             when paired with a beacon node that has this endpoint implemented. This flag will be enabled by default in
@@ -84,10 +84,7 @@ OPTIONS:
             subscriptions only.
         --builder-boost-factor <INTEGER>
             Percentage multiplier to apply to the builder's payload value when choosing between a
-            builder payload header and payload from the paired execution node. This parameter is only
-            relevant if the beacon node is connected to a builder, deems it safe to produce a builder
-            payload, and receives valid responses from both the builder endpoint and the paired
-            execution node.
+            builder payload header and payload from the paired execution node.
         --builder-registration-timestamp-override <builder-registration-timestamp-override>
             This flag takes a unix timestamp value that will be used to override the timestamp used in the builder api
             registration

book/src/help_vm_create.md

@@ -44,10 +44,7 @@ OPTIONS:
             validator being created twice and therefore slashable conditions.
         --builder-boost-factor <INTEGER>
             Percentage multiplier to apply to the builder's payload value when choosing between a
-            builder payload header and payload from the paired execution node. This parameter is only
-            relevant if the beacon node is connected to a builder, deems it safe to produce a builder
-            payload, and receives valid responses from both the builder endpoint and the paired
-            execution node.
+            builder payload header and payload from the paired execution node.
         --builder-proposals <builder-proposals>
             When provided, all created validators will attempt to create blocks via builder rather than the local EL.
             [possible values: true, false]

book/src/help_vm_move.md

@@ -28,10 +28,7 @@ FLAGS:
 OPTIONS:
         --builder-boost-factor <INTEGER>
             Percentage multiplier to apply to the builder's payload value when choosing between a
-            builder payload header and payload from the paired execution node. This parameter is only
-            relevant if the beacon node is connected to a builder, deems it safe to produce a builder
-            payload, and receives valid responses from both the builder endpoint and the paired
-            execution node.
+            builder payload header and payload from the paired execution node.
         --builder-proposals <builder-proposals>
             When provided, all created validators will attempt to create blocks via builder rather than the local EL.
             [possible values: true, false]
@@ -82,7 +79,7 @@ OPTIONS:
             Name of the Eth2 chain Lighthouse will sync and follow. [possible values: mainnet, prater, goerli, gnosis,
             chiado, sepolia, holesky]
         --prefer-builder-proposals <builder-proposals>
-            When provided, all created validators will always prefer blocks from builder rather than the local EL, regardless 
+            When provided, all created validators will always prefer blocks from the builder rather than the local EL, regardless 
             of the builder payload value.
             [possible values: true, false]
         --safe-slots-to-import-optimistically <INTEGER>

validator_client/src/cli.rs

@@ -364,7 +364,7 @@ pub fn cli_app<'a, 'b>() -> App<'a, 'b> {
             Arg::with_name("prefer-builder-proposals")
                 .long("prefer-builder-proposals")
                 .help("If this flag is set, Lighthouse will always prefer blocks \
-                    constructed by builders, if available.")
+                    constructed by builders, regardless of payload value.")
                 .takes_value(false),
         )
 }

validator_manager/src/create_validators.rs

@@ -203,7 +203,7 @@ pub fn cli_app<'a, 'b>() -> App<'a, 'b> {
                 .long(PREFER_BUILDER_PROPOSALS_FLAG)
                 .help(
                     "If this flag is set, Lighthouse will always prefer blocks \
-                    constructed by builders, if available.",
+                    constructed by builders, regardless of payload value.",
                 )
                 .required(false)
                 .possible_values(&["true", "false"])

validator_manager/src/move_validators.rs

@@ -190,7 +190,7 @@ pub fn cli_app<'a, 'b>() -> App<'a, 'b> {
                 .long(PREFER_BUILDER_PROPOSALS_FLAG)
                 .help(
                     "If this flag is set, Lighthouse will always prefer blocks \
-                    constructed by builders, if available.",
+                    constructed by builders, regardless of payload value.",
                 )
                 .required(false)
                 .possible_values(&["true", "false"])