When de-authing, fix image and cooldown period

[theref]

[derekpierre]

Does this issue envision anything more involved than a simple modification to image like the following.

Of course it can change in the medium term, but in the shorter term, is this sufficient?

cc @arjunhassard , @theref , @cygnusv

[derekpierre]

Image fixed via #686 , not cooldown period text.

[derekpierre]

What is the expected cool-down period for TACo - is it fixed at 6-months or does it vary based on lock-up period? Is de-auth prevented before the appropriate time has passed before the cool down can be initiated?

@cygnusv , @vzotova , @arjunhassard , @theref

[vzotova]

for TACo - fixed 6 months, besides that - commitment period when you are not able to request decrease. And other note - during deauth period (or cooldown, whatever) you can start (overwrite existing one) another decrease request and also increase auth at any moment

[derekpierre]

So are we good with just putting 6 months then as the cool down period.

If we want to provide more context, perhaps that can be addressed in the docs somewhere? There is this section currently - https://docs.threshold.network/staking-and-running-a-node/pre-node-setup/duties-and-compensation#deauthorization-delay - though pretty straightforward anyway.