diff --git a/documentation/en/default-lotus-miner-config.toml b/documentation/en/default-lotus-miner-config.toml
index cec6e921d..634da3b9d 100644
--- a/documentation/en/default-lotus-miner-config.toml
+++ b/documentation/en/default-lotus-miner-config.toml
@@ -337,6 +337,7 @@
   # env var: LOTUS_SEALING_MAXSEALINGSECTORSFORDEALS
   #MaxSealingSectorsForDeals = 0
 
+  # Prefer creating new sectors even if there are sectors Available for upgrading.
   # This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
   # possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing
   # flow when the volume of storage deals is lower.
diff --git a/itests/sector_make_cc_avail_test.go b/itests/sector_make_cc_avail_test.go
index 998ce08d5..10c068370 100644
--- a/itests/sector_make_cc_avail_test.go
+++ b/itests/sector_make_cc_avail_test.go
@@ -74,4 +74,4 @@ func TestMakeAvailable(t *testing.T) {
 	miner.WaitSectorsProving(ctx, map[abi.SectorNumber]struct{}{
 		CCUpgrade: {},
 	})
-}
\ No newline at end of file
+}
diff --git a/itests/sector_prefer_no_upgrade_test.go b/itests/sector_prefer_no_upgrade_test.go
index 5b0837607..e7e0e60fd 100644
--- a/itests/sector_prefer_no_upgrade_test.go
+++ b/itests/sector_prefer_no_upgrade_test.go
@@ -87,4 +87,3 @@ func TestPreferNoUpgrade(t *testing.T) {
 		})
 	}
 }
-
diff --git a/node/config/doc_gen.go b/node/config/doc_gen.go
index 4927b48d2..ba5ffcc03 100644
--- a/node/config/doc_gen.go
+++ b/node/config/doc_gen.go
@@ -726,7 +726,8 @@ Note that setting this number too high in relation to deal ingestion rate may re
 			Name: "PreferNewSectorsForDeals",
 			Type: "bool",
 
-			Comment: `This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
+			Comment: `Prefer creating new sectors even if there are sectors Available for upgrading.
+This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
 possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing
 flow when the volume of storage deals is lower.`,
 		},
diff --git a/node/config/types.go b/node/config/types.go
index 0a5d6876d..b3ba36c7f 100644
--- a/node/config/types.go
+++ b/node/config/types.go
@@ -234,8 +234,7 @@ type SealingConfig struct {
 	// Upper bound on how many sectors can be sealing+upgrading at the same time when creating new sectors with deals (0 = unlimited)
 	MaxSealingSectorsForDeals uint64
 
-	// Prefer creating new sectors even if there are sectors Available for upgrading
-	//
+	// Prefer creating new sectors even if there are sectors Available for upgrading.
 	// This setting combined with MaxUpgradingSectors set to a value higher than MaxSealingSectorsForDeals makes it
 	// possible to use fast sector upgrades to handle high volumes of storage deals, while still using the simple sealing
 	// flow when the volume of storage deals is lower.