changes for vault tier

.github/PULL_REQUEST_TEMPLATE/control_plane_template.md

@@ -4,7 +4,7 @@
 
 Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
 
-![diagram](https://github.com/Azure/azure-rest-api-specs/assets/4429827/b321e1dc-5e07-4940-9cd6-a65ac6729a8b)
+![diagram](https://github.com/Azure/azure-rest-api-specs/assets/4429827/029a11fd-eaf9-4865-9d77-a16b5ea5eb26)
 
 [1] [ARM review queue] (for **merge** queues, see [4])  
 The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page. 

.github/PULL_REQUEST_TEMPLATE/data_plane_template.md

@@ -47,13 +47,13 @@ The [Azure API Review Board](https://aka.ms/azsdk/onboarding/restapischedule) is
 ### Tooling
 
  * [Open API validation tools](https://aka.ms/swaggertools) were run on this PR. Go here to see [how to fix errors](https://aka.ms/ci-fix)
- * [Spectral Linting](https://aka.ms/style)
+ * [Spectral Linting](https://github.com/Azure/azure-api-style-guide/blob/main/README.md)
  * [Open API Hub](https://aka.ms/openapiportal)
 
 ### Guidelines & Specifications
 
- * [Azure REST API Guidelines](https://aka.ms/guidelines)
- * [OpenAPI Style Guidelines](https://aka.ms/style)
+ * [Azure REST API Guidelines](https://aka.ms/azapi/guidelines)
+ * [OpenAPI Style Guidelines](https://aka.ms/azapi/style)
  * [Azure Breaking Change Policy](https://aka.ms/AzBreakingChangesPolicy)
 
 ### Helpful Links

.github/policies/resourceManagement.yml

@@ -2529,7 +2529,16 @@ configuration:
       then:
       - removeLabel:
           label: no-recent-activity
-      description: 
+      description:
+    - if:
+      - payloadType: Pull_Request
+      then:
+      - if:
+        - filesMatchPattern:
+            pattern: specification/.*(\.tsp|tspconfig.yaml)
+        then:
+        - addLabel:
+            label: TypeSpec
     - if:
       - payloadType: Pull_Request
       then:

.gitignore

@@ -121,5 +121,5 @@ warnings.txt
 *.bak
 
 # Eng Tools
-eng/tools/TypeSpecValidation/dist
-!eng/tools/TypeSpecValidation/cmd/*.js
+eng/tools/typespec-validation/dist
+!eng/tools/typespec-validation/cmd/*.js

README.md

@@ -168,7 +168,7 @@ If the AutoRest configuration file (aka. the readme.md) is placed out of sub-ser
 
 ### common-types
 
-Specification files and AutoRest configuration files in one RP folder are better to refer to files in the same RP folder. Entity type definition that can be shared cross resource providers or services should to be placed and maintained either under the folder [**common-types**](https://github.com/Azure/azure-rest-api-specs#common-types) under specification, or under **common-types** folder of service group folder structure. The former supports the entity type sharing cross rp folders, while the latter supports the enitity type sharing cross components or services under the same rp folder.
+Specification files and AutoRest configuration files in one RP folder are better to refer to files in the same RP folder. Entity type definition that can be shared cross resource providers or services should to be placed and maintained either under the folder [**common-types**](https://github.com/Azure/azure-rest-api-specs#common-types) under specification, or under **common-types** folder of service group folder structure. The former supports the entity type sharing cross rp folders, while the latter supports the entity type sharing cross components or services under the same rp folder.
 
 Refer to [Resource-Management](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/common-types/resource-management) common types for example.