docs: howto unlock tf state

Author: iru

CONTRIBUTE.md

@@ -83,8 +83,16 @@ Implemented vía **Terraform Kitchen** | https://newcontext-oss.github.io/kitche
 
 Because CI/CD sometimes fail, we setup the Terraform state to be handled in backend (s3+dynamo) within the Sysdig AWS backend (sysdig-test-account).
 
-#### Howto unlock terraform backend
+#### Remote state cleanup from local
 
+In case you need to handle terraform backend state from failing kitchen tests, some guidance for using the `backend.tf` remote state manifest, present on each test
+ - Configure same parameters as the github action, that is `AWS_PROFILE`, and leave default `name` and `region` values
+ - Kitchen works with `terraform workspaces` so, in case you want to fix a specific test, switch to that workspace after the `terraform init` with `terraform workspace select WORKSPACE`
+ - Perform the desired terraform task
+
+You can also use `kitchen destroy` instead of `terraform` but the requirements are the same, except that the workspace will be managed through kitchen
+
+#### State unlock
 ```
 # go to the specific test ex.:
 cd test/fixtures/single-subscription
@@ -96,15 +104,6 @@ terraform workspace select kitchen-terraform-WORKSPACE_NAME
 terraform force-unlock LOCK_ID
 ```
 
-### Remote state cleanup from local
-
-In case you need to handle terraform backend state from failing kitchen tests, some guidance for using the `backend.tf` remote state manifest, present on each test
- - Configure same parameters as the github action, that is `AWS_PROFILE`, and leave default `name` and `region` values
- - Kitchen works with `terraform workspaces` so, in case you want to fix a specific test, switch to that workspace after the `terraform init` with `terraform workspace select WORKSPACE`
- - Perform the desired terraform task
-
-You can also use `kitchen destroy` instead of `terraform` but the requirements are the same, except that the workspace will be managed through kitchen
-
 
 ### Running Kitchen tests locally