Update policy section titles and descriptions in governance document

Author: D1M1TR10S

docs/policies-and-governance.md

@@ -83,13 +83,13 @@ Access is always constrained by GitHub's public API permission model and the aut
 
 > **Important:** This policy provides comprehensive control over GitHub MCP Server access in Copilot editors. When disabled, users in affected applications will not be able to use the GitHub MCP Server regardless of deployment mode (remote or local) or authentication method.
 
-#### Legacy: Editor Preview Policy
+#### Temporary: Copilot Editor Preview Policy
 
 * **Policy:** Editor Preview Features  
-* **Status:** Being phased out as editors migrate to the "MCP servers in Copilot" policy above
+* **Status:** Being phased out as editors migrate to the "MCP servers in Copilot" policy above, and once the Remote GitHub MCP server goes GA
 * **What it controls:** When disabled, prevents remaining Copilot editors from using the Remote GitHub MCP Server through OAuth connections in all first-party and third-party host applications (does not affect local deployments or PAT authentication)
 
-> **Note:** As Copilot editors migrate from the Editor Preview Policy to the "MCP servers in Copilot" policy, the scope of control becomes more centralized, blocking both remote and local GitHub MCP Server access when disabled. Access in third-party hosts is governed separately by OAuth App, GitHub App, and PAT policies.
+> **Note:** As Copilot editors migrate from the "Copilot Editor Preview" policy to the "MCP servers in Copilot" policy, the scope of control becomes more centralized, blocking both remote and local GitHub MCP Server access when disabled. Access in third-party hosts is governed separately by OAuth App, GitHub App, and PAT policies.
 
 ### 2. Third-Party Host Apps (e.g., Claude, Cursor, Windsurf) → OAuth App or GitHub App Controls