Fix GCP docs accuracy: legacy tokeninfo endpoint, region placeholder, typos

src/pentesting-cloud/gcp-security/gcp-basic-information/README.md

@@ -315,7 +315,7 @@ Google actually [recommends](https://cloud.google.com/compute/docs/access/servic
 You can see what **scopes** are **assigned** by **querying:**<sup>[[20]](#references)</sup>
 
 ```bash
-curl 'https://www.googleapis.com/oauth2/v1/tokeninfo?access_token=<access_token>'
+curl 'https://oauth2.googleapis.com/tokeninfo?access_token=<access_token>'
 
 {
   "issued_to": "223044615559.apps.googleusercontent.com",

src/pentesting-cloud/gcp-security/gcp-post-exploitation/gcp-kms-post-exploitation.md

@@ -139,7 +139,7 @@ gcloud kms import-jobs create my-import-job \
 # Generate key material
 openssl rand -out my-key-material.bin 32
 
-# Import the Key Material (it's encrypted with an asymetrict key of the import job previous to be sent)
+# Import the Key Material (it's encrypted with an asymmetric key of the import job previous to be sent)
 gcloud kms keys versions import \
     --import-job my-import-job \
     --location us-central1 \

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

@@ -63,7 +63,7 @@ This is what makes the deploy path a **privesc primitive**: unless another ident
 ../gcp-services/gcp-app-engine-enum.md
 {{#endref}}
 
-The URL of the application is something like `https://<proj-name>.oa.r.appspot.com/` or `https://<service_name>-dot-<proj-name>.oa.r.appspot.com`.<sup>[[7]](#references)</sup>
+The URL of the application is something like `https://<proj-name>.<REGION_ID>.r.appspot.com/` or `https://<service_name>-dot-<proj-name>.<REGION_ID>.r.appspot.com` (where `<REGION_ID>` is the region code, e.g. `uc` for `us-central`).<sup>[[7]](#references)</sup>
 
 ### Update equivalent permissions
 

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

@@ -36,7 +36,7 @@ The `secretmanager.secrets.setIamPolicy` permission lets a principal change a se
 <details><summary>Add IAM policy binding to secret</summary>
 
 ```bash
-gcloud secrets add-iam-policy-binding <scret-name> \
+gcloud secrets add-iam-policy-binding <secret-name> \
   --member="serviceAccount:<sa-name>@$PROJECT_ID.iam.gserviceaccount.com" \
   --role="roles/secretmanager.secretAccessor"
 ```