fix

Author: carlospolop

src/pentesting-cloud/azure-security/az-post-exploitation/az-function-apps-post-exploitation.md

@@ -10,7 +10,8 @@ For more information about function apps check:
 ../az-services/az-function-apps.md
 {{#endref}}
 
-> [!CAUTION] > **Function Apps post exploitation tricks are very related to the privilege escalation tricks** so you can find all of them there:
+> [!CAUTION]
+> **Function Apps post exploitation tricks are very related to the privilege escalation tricks** so you can find all of them there:
 
 {{#ref}}
 ../az-privilege-escalation/az-functions-app-privesc.md

src/pentesting-cloud/gcp-security/gcp-privilege-escalation/gcp-storage-privesc.md

@@ -65,7 +65,7 @@ gcloud config set pass_credentials_to_gsutil true
 
 Another exploit script for this method can be found [here](https://github.com/RhinoSecurityLabs/GCP-IAM-Privilege-Escalation/blob/master/ExploitScripts/storage.hmacKeys.create.py).
 
-## `storage.objects.create`, `storage.objects.delete` = Storage Write permissions
+### `storage.objects.create`, `storage.objects.delete` = Storage Write permissions
 
 In order to **create a new object** inside a bucket you need `storage.objects.create` and, according to [the docs](https://cloud.google.com/storage/docs/access-control/iam-permissions#object_permissions), you need also `storage.objects.delete` to **modify** an existent object.