Doc for 1.11.2

docs/mine/lotus/message-pool.md

@@ -69,7 +69,11 @@ You can replace messages in the pool by pushing a new message with the same `Non
 lotus mpool replace --auto <from> <nonce>
 ```
 
-The above command will replace the associated message in the pool and automatically reprice it with a new _GasPremium_ and _GasFeeCap_ as estimated from the current network conditions. You can also set `--max-fee` if you wish to limit the total amount to spend for the message. All other flags are ignored.
+The above command will replace the associated message in the pool and automatically reprice it with a new _GasPremium_ and _GasFeeCap_ as estimated from the current network conditions. You can also set `--fee-limit` if you wish to limit the total amount to spend for the message. All other flags are ignored.
+
+::: warning
+`--fee-limit` uses units of FIL with decimals support, whereas `--max-fee` uses `attoFIL`.
+:::  
 
 Alternatively, the _GasPremium_, _GasFeeCap_ can be set manually with their respective flags:
 

docs/mine/lotus/miner-addresses.md

@@ -113,6 +113,12 @@ To set up a _control address_:
 
 Repeat this procedure to add additional addresses.
 
+5. You can specify other actor to check control address:
+
+```shell
+lotus-miner --actor f01000 actor control list
+```
+
 ### Use control addresses for commits
 
 Clean up the tasks required for your worker address by setting your control addresses to perform pre-commits and commits. With this, only market messages are sent from the worker address. If the basefee is high, then you can still put sectors on chain without those messages being blocked by things like publishing deals.

docs/mine/lotus/miner-configuration.md

@@ -189,6 +189,13 @@ This section controls some of the behavior around sector sealing:
   MaxSealingSectors = 0
   # Upper bound on how many sectors can be sealing at the same time when creating new sectors with deals (0 = unlimited)
   MaxSealingSectorsForDeals = 0
+  # CommittedCapacitySectorLifetime is the duration a Committed Capacity (CC) sector will
+  # live before it must be extended or converted into sector containing deals before it is
+  # terminated. Value must be between 180-540 days inclusive
+  #
+  # type: Duration
+  CommittedCapacitySectorLifetime = "12960h0m0s"
+
   # Period of time that a newly created sector will wait for more deals to be packed in to before it starts to seal.
   # Sectors which are fully filled will start sealing immediately
   WaitDealsDelay = "6h0m0s"
@@ -347,6 +354,19 @@ Batch 1:
 		19	OK
 ```
 
+### CommittedCapacitySectorLifetime
+
+The available units are:
+
+```
+"ms": int64(Millisecond),  
+ "s":  int64(Second),  
+ "m":  int64(Minute),   
+ "h":  int64(Hour),
+```
+
+For example, if you want to set the sector lifecycle to 180 days, you can multiply 180 days by 24 hours per day to get 4320 hours and set this value to `"4320h0m0s"`.
+
 ## Storage section
 
 The storage sector controls whether the miner can perform certain sealing actions. Depending on the setup and the use of additional [seal workers](seal-workers.md), you may want to modify some of the options.

docs/mine/lotus/sector-pledging.md

@@ -75,3 +75,58 @@ lotus-miner sectors mark-for-upgrade <sector number>
 ```
 
 The sector should become inactive within 24 hours after a new replacement sector has sealed. From that point, the pledged storage can be re-used for new sectors.
+
+## Inspect expiring sectors
+
+You can check which sectors are about to expire. Sectors that will expire within 60 days can be checked by default with the following command:
+
+```shell
+lotus-miner sectors check-expire
+```
+
+If you want to check for sectors that will expire within 33 days (669600 epoch in devnet) , add the `--cutoff` option along with your desired epoch:
+
+```shell with-output
+lotus-miner sectors check-expire --cutoff 669600
+```
+
+```shell output
+ID  SealProof  InitialPledge  Activation                      Expiration                  MaxExpiration                 MaxExtendNow                  
+5   5          59.605 nFIL    1519 (1 day 9 hours ago)        691857 (in 4 weeks 2 days)  5257519 (in 34 weeks 3 days)  1587303 (in 10 weeks 2 days)  
+10  5          59.605 nFIL    3588 (1 day 7 hours ago)        697617 (in 4 weeks 2 days)  5259588 (in 34 weeks 4 days)  1587303 (in 10 weeks 2 days)  
+11  5          59.605 nFIL    4695 (1 day 6 hours ago)        697617 (in 4 weeks 2 days)  5260695 (in 34 weeks 4 days)  1587303 (in 10 weeks 2 days)  
+15  5          59.605 nFIL    6891 (1 day 4 hours ago)        700497 (in 4 weeks 2 days)  5262891 (in 34 weeks 4 days)  1587303 (in 10 weeks 2 days)  
+17  5          59.605 nFIL    7004 (1 day 3 hours ago)        700497 (in 4 weeks 2 days)  5263004 (in 34 weeks 4 days)  1587303 (in 10 weeks 2 days)
+```
+
+## Extend sectors
+
+You can extend the lifecycle of a sector with the command:
+
+```shell
+lotus-miner sectors renew [command options] [arguments...]
+```
+
+This is an example of selecting sectors with a lifecycle between `epochnumber-a` epoch and `epochnumber-b` epoch and updating it to 1555200 epoch:
+
+```shell
+lotus-miner sectors renew  --from <epochnumber-a> --to <epochnumber-b> --new-expiration 1555200
+```
+
+This is an example of updating the lifecycle of a sector read from a file to 1555200 epoch:
+
+```shell
+lotus-miner sectors renew  --sector-file <your-sectorfile> --new-expiration 1555200
+```
+
+::: warning
+You have to select the sectors to renew. That means you have to specify the `--from` and `--to` option, or specify the sector file, if no sector is selected this command will have no effect.
+
+Format of sector file:
+
+```  
+1  
+2  
+...
+```  
+:::

docs/mine/lotus/split-markets-miners.md

@@ -487,10 +487,10 @@ lotus-miner actor set-addrs <NEW_MULTIADDR>
 
 ```toml
 [Addresses]  
-  \#PreCommitControl = ["f00XX1"]  
-  \# CommitControl = ["f00XX2"]  
+    PreCommitControl = ["f00XX1"]  
+    CommitControl = ["f00XX2"]  
     TerminateControl = []  
-  \#  DealPublishControl = ["f00XX3"] 
+    DealPublishControl = ["f00XX3"] 
     DisableOwnerFallback = false  
     DisableWorkerFallback = false 
 ```