Improvements to cert-syncs

docs/api-reference/endpoints/pki/syncs/azure-key-vault/remove-certificates.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Remove Certificates from Azure Key Vault"
-openapi: "POST /api/v1/pki/syncs/azure-key-vault/{pkiSyncId}/remove"
+openapi: "POST /api/v1/pki/syncs/azure-key-vault/{pkiSyncId}/remove-certificates"
 ---
 
 <Warning>
@@ -29,7 +29,7 @@ This endpoint removes certificates from the specified Azure Key Vault that are n
 
 <RequestExample>
 ```bash cURL
-curl -X POST "https://app.infisical.com/api/v1/pki/syncs/azure-key-vault/ps_12345/remove" \
+curl -X POST "https://app.infisical.com/api/v1/pki/syncs/azure-key-vault/ps_12345/remove-certificates" \
   -H "Authorization: Bearer <your-api-key>"
 ```
 </RequestExample>

docs/api-reference/endpoints/pki/syncs/options.mdx

@@ -10,7 +10,7 @@ This endpoint lists all available PKI sync destination options and their capabil
 ## Request
 
 <ParamField query="projectId" type="string" optional>
-  Project ID (for authorization purposes, but the options are global)
+  Project ID
 </ParamField>
 
 ## Response

docs/docs.json

@@ -2646,9 +2646,9 @@
     "href": "https://infisical.com"
   },
   "api": {
-    "openapi": "https://api.infisical.com/api/docs/json",
+    "openapi": "https://app.infisical.com/api/docs/json",
     "mdx": {
-      "server": ["https://api.infisical.com"]
+      "server": ["https://app.infisical.com"]
     }
   },
   "appearance": {

docs/documentation/platform/pki/certificate-syncs/overview.mdx

@@ -80,8 +80,7 @@ via the UI or API for the third-party service you intend to sync certificates to
       - Certificate naming schema to control how certificate names are generated in the destination
 
 <Note>
-    Certificate Syncs manage certificates that are prefixed with "Infisical-" in the destination. Only
-    certificates managed by Infisical will be affected during sync operations. Certificates not created or
+    Only certificates managed by Infisical will be affected during sync operations. Certificates not created or
     managed by Infisical will remain untouched, and changes made to Infisical-managed certificates directly
     in the destination service may be overwritten by future syncs.
 </Note>
@@ -110,11 +109,9 @@ By default, certificates are named using the pattern `Infisical-{certificateId}`
 You can customize certificate naming by providing a **Certificate Name Schema** when creating or updating a Certificate Sync. The schema supports the following placeholders:
 
 - `{{certificateId}}` - The unique certificate identifier (required)
-- `{{environment}}` - The environment context (always "global" for PKI syncs)
 
 **Examples:**
 - `myapp-{{certificateId}}` → `myapp-abc123def456`
-- `{{environment}}-cert-{{certificateId}}` → `global-cert-abc123def456`
 - `ssl/{{certificateId}}` → `ssl/abc123def456`
 
 **Rules:**