update all references to editor or editor view

content/blog/esc-env-run-aws/index.md

@@ -122,13 +122,13 @@ After creating your role, make sure to make a note of your role’s ARN value as
 
 ### Step 3: Create a new environment
 
-Now that we’ve created all the necessary AWS resources, let’s move over to the Pulumi side of things. You’ll first want to create a new environment in the [Pulumi Cloud](https://app.pulumi.com/). Make sure that you have the correct organization selected in the left-hand navigation menu. Then click the **Environments** link, and click the **Create environment** button. In the following pop-up, provide a name for your environment before clicking the  **Create environment** button.
+Now that we’ve created all the necessary AWS resources, let’s move over to the Pulumi side of things. You’ll first want to create a new environment in the [Pulumi Cloud](https://app.pulumi.com/). Make sure that you have the correct organization selected in the left-hand navigation menu. Then click the **Environments** link, and click the **Create environment** button. In the following pop-up, provide a name for your environment before clicking the **Create environment** button.
 
 {{< video title="Creating a new Pulumi ESC environment" src="https://www.pulumi.com/uploads/create-new-environment.mp4" autoplay="true" loop="true" >}}
 
 ### Step 4: Add the AWS provider integration
 
-Once you’ve created your new environment, you will be presented with a split-pane editor view. You’ll want to clear out the default placeholder content in the editor on the left-hand side and replace it with the following code, making sure to replace `<your-oidc-iam-role-arn>` with the value of your IAM role ARN from the previous step:
+Once you’ve created your new environment, you will be presented with a split-pane document view. You’ll want to clear out the default placeholder content in the editor on the left-hand side and replace it with the following code, making sure to replace `<your-oidc-iam-role-arn>` with the value of your IAM role ARN from the previous step:
 
 ```yaml
 values:

content/blog/esc-key-value-table-editor-launch/index.md

@@ -1,8 +1,8 @@
 ---
-title: "Introducing the Key-Value Table Editor for Pulumi ESC"
+title: "Introducing the Table view for Pulumi ESC"
 date: 2024-03-26T00:00:00-07:00
 draft: false
-meta_desc: "The Key-Value Table Editor introduces a new visual interface for managing configuration and secrets using Pulumi ESC."
+meta_desc: "The Table view introduces a new visual interface for managing configuration and secrets using Pulumi ESC."
 meta_image: "meta.png"
 authors:
   - arun-loganathan
@@ -15,34 +15,34 @@ tags:
 ---
 
 
-We're excited to announce the launch of the Pulumi Environments, Secrets, and Configurations ([ESC](/product/esc)) Key-Value Table Editor. At Pulumi, we're committed to providing flexible solutions that cater to diverse development needs and practices. This latest addition underscores our dedication to this principle by offering a user-friendly interface for managing complex configurations and secrets.
+We're excited to announce the launch of the Pulumi Environments, Secrets, and Configurations ([ESC](/product/esc)) Table view. At Pulumi, we're committed to providing flexible solutions that cater to diverse development needs and practices. This latest addition underscores our dedication to this principle by offering a user-friendly interface for managing complex configurations and secrets.
 
 Pulumi ESC simplifies the management of secrets and configurations by reducing duplication and drift, empowering development teams to focus on building and deploying. The existing YAML-based code editor offers a native way for developers to author and manage configurations.
 
 <!--more-->
 
-The Key-Value Table Editor we are launching today introduces an alternate visual interface for handling configuration tasks, enabling the direct input of plaintext and secret values.  Key capabilities of the Table Editor include:
+The Table view we are launching today introduces an alternate visual interface for handling configuration tasks, enabling the direct input of plaintext and secret values.  Key capabilities of the Table Editor include:
 
 - **CRUD Operations**: Perform Create, Read, Update, and Delete (CRUD) operations on your secrets and  plaintext values
 - **Decrypting Secrets**: Safely decrypt secrets one at a time, directly within the editor
 - **Environment Imports**: [Import environments](/docs/esc/environments/#importing-other-environments) and define the order of imports to suit your project's needs
 - **Variables Projections**: Make variables available as [Pulumi Config](/docs/esc/environments/#using-environments-with-pulumi-iac), [environment variables](/docs/esc/environments/#projecting-environment-variables), and files, streamlining your deployment and runtime configuration.
 - **Interpolations and References**: Add references to existing path-values, or add [interpolations](/docs/esc/environments/#interpolating-values) to dynamically generate values
 
-![Key-Value Table Editor](esc-key-value-table-editor.png)
+![Table view](esc-key-value-table-editor.png)
 
 In the current release of the Table view, [provider configurations](/docs/esc/integrations) and functions are set to read-only.  
 
 ## What’s Next?
 
-Looking to the future, we are already working on the next set of enhancements for the Key-Value Table Editor. Soon, you will have the capability to add and edit provider configurations directly within the table view.
+Looking to the future, we are already working on the next set of enhancements for the Table view. Soon, you will have the capability to add and edit provider configurations directly within the table view.
 
 Pulumi ESC's diverse array of providers not only allows teams to dynamically acquire cloud provider credentials at runtime, thus eliminating the need for static, long-lived credentials but also enables retrieving secrets from external secrets managers, such as AWS Secrets Manager and HashiCorp Vault, directly within ESC. This means users can seamlessly pull and utilize secrets within ESC, enhancing security and flexibility. The upcoming provider configuration support in the Table view will offer a guided experience, simplifying the process of leveraging Pulumi ESC's comprehensive set of providers.
 
 ## Conclusion
 
-The launch of the Key-Value Table Editor marks an important step in our mission to make infrastructure as code more accessible and manageable for developers.
+The launch of the Table view marks an important step in our mission to make infrastructure as code more accessible and manageable for developers.
 
-Your [feedback](https://github.com/pulumi/esc/issues/new/choose) is the cornerstone of our development process. As we look ahead, we're focusing on incorporating your insights to further enhance the Key-Value Table Editor. Together, we can continue to refine and advance Pulumi ESC, making it an even more powerful tool for the developer community.
+Your [feedback](https://github.com/pulumi/esc/issues/new/choose) is the cornerstone of our development process. As we look ahead, we're focusing on incorporating your insights to further enhance the Table view. Together, we can continue to refine and advance Pulumi ESC, making it an even more powerful tool for the developer community.
 
 Check out our [documentation](/docs/esc) to learn more about Pulumi ESC.

content/blog/esc-table-editor-provider-config-support/index.md

@@ -3,7 +3,7 @@ title: "Pulumi ESC Table Editor Now Supports Dynamic Credential and Secret Integ
 date: 2024-09-10T00:00:00-07:00
 draft: false
 allow_long_title: true
-meta_desc: "The Key-Value Table Editor introduces a new visual interface for managing provider configuration using Pulumi ESC."
+meta_desc: "The Table view introduces a new visual interface for managing provider configuration using Pulumi ESC."
 meta_image: "meta.png"
 authors:
 - kimberley-mackenzie
@@ -16,7 +16,7 @@ tags:
   - releases
 ---
 
-We are pleased to announce a major update to the [Pulumi ESC](/product/esc)’s Table Editor: full support for provider configurations is now live! When we [first introduced the ESC Key-Value Table Editor](/blog/esc-key-value-table-editor-launch), our goal was to offer a user-friendly interface for managing complex configuration and secrets for your applications and infrastructure. This has empowered teams to focus on what they do best—building and deploying software.
+We are pleased to announce a major update to the [Pulumi ESC](/product/esc)’s Table Editor: full support for provider configurations is now live! When we [first introduced the ESC Table view](/blog/esc-key-value-table-editor-launch), our goal was to offer a user-friendly interface for managing complex configuration and secrets for your applications and infrastructure. This has empowered teams to focus on what they do best—building and deploying software.
 
 In our initial launch, the Table Editor allowed you to perform CRUD operations on your secrets and plaintext values, decrypt secrets, import environments, and manage variables—all within a visual interface. Today, we’re taking the next step by enabling full read-write support for provider configurations within the Table Editor. This new capability allows you to add, edit, and manage your provider configurations directly from the table view, offering a more integrated and seamless experience.
 
@@ -31,12 +31,12 @@ In our initial launch, the Table Editor allowed you to perform CRUD operations o
 
 ## Enhancing the Table Editor: Provider Configuration Support
 
-With the addition of provider configuration support in the Key-Value Table Editor, incorporating Pulumi ESC provider capabilities into your workflow is now more straightforward. A clean, user-friendly form provides step-by-step guidance, promoting best practices like [OIDC](/docs/pulumi-cloud/oidc/) adoption and the secure handling of sensitive data. This streamlined approach reduces the need for external documentation, making the entire process more intuitive and efficient.
+With the addition of provider configuration support in the Table view, incorporating Pulumi ESC provider capabilities into your workflow is now more straightforward. A clean, user-friendly form provides step-by-step guidance, promoting best practices like [OIDC](/docs/pulumi-cloud/oidc/) adoption and the secure handling of sensitive data. This streamlined approach reduces the need for external documentation, making the entire process more intuitive and efficient.
 
-![Key-Value Table Editor](esc-table-editor-provider-config.png)
+![Table view](esc-table-editor-provider-config.png)
 
 ## Conclusion
 
-The new provider configuration support in the ESC Key-Value Table Editor marks another step in our efforts to simplify and enhance the developer experience. We’re eager to see how you’ll leverage this new capability to streamline your workflows and strengthen your infrastructure’s security. As always, your feedback is invaluable to our development process, and we’re committed to continually improving the Table Editor and other Pulumi tools based on your needs. Please share your feedback with us [here](https://github.com/pulumi/esc/issues/new/choose).
+The new provider configuration support in the ESC Table view marks another step in our efforts to simplify and enhance the developer experience. We’re eager to see how you’ll leverage this new capability to streamline your workflows and strengthen your infrastructure’s security. As always, your feedback is invaluable to our development process, and we’re committed to continually improving the Table Editor and other Pulumi tools based on your needs. Please share your feedback with us [here](https://github.com/pulumi/esc/issues/new/choose).
 
 Check out our [documentation](/docs/esc) to learn more about Pulumi ESC.

content/blog/esc-webhooks-launch/index.md

@@ -33,7 +33,7 @@ Setting up Webhooks is straightforward. You can use the Pulumi Cloud Console, th
 - Select your desired integration (Slack, Microsoft Teams, Pulumi Deployments, or generic JSON Webhooks).
 - Configure the Webhook details, including the events you want to trigger notifications on.
 
-![Key-Value Table Editor](esc-webhooks.png)
+![Table view](esc-webhooks.png)
 
 ### Using Pulumi Service Provider
 

content/blog/pulumi-esc-ga/index.md

@@ -47,7 +47,7 @@ Pulumi ESC is the modern secret management platform designed to streamline and s
 - **Gain Complete Visibility and Control**: Track all secret access and changes with detailed audit logs. Understand the downstream impact of changes and ensure your secrets are used securely and consistently across your organization.
 - **Secrets as Code**: Pulumi ESC supports flexible composition of environments by allowing [imports](/docs/esc/get-started/import-environments/) between one another. Construct hierarchical environments that avoid the need to copy/paste secrets and configurations, ensuring that changes are consistently propagated across all related environments.
 
-![Pulumi ESC Editor View](esc-document-editor-view.png)
+![Pulumi ESC document view](esc-document-editor-view.png)
 
 #### Built for the Modern Cloud, Open by Design:
 - **Use It Your Way**: Pulumi ESC integrates seamlessly with other Pulumi products and features such as Pulumi IaC and Pulumi Deployments for a unified infrastructure management experience. But its flexibility extends to any platform or toolset, including HashiCorp Terraform.

content/blog/pulumi-release-notes-103/index.md

@@ -18,7 +18,7 @@ As always, we have been actively rolling out new features in response to the inv
 
 - [Pulumi Cloud](#pulumi-cloud)
   - [Pulumi ESC 1Password Support](#pulumi-esc-1password-support)
-  - [Pulumi ESC Key-Value Table Editor](#pulumi-esc-key-value-table-editor)
+  - [Pulumi ESC Table view](#pulumi-esc-key-value-table-editor)
   - [Pulumi ESC YAML Code Editor Enhancements](#pulumi-esc-yaml-code-editor-enhancements)
   - [Pulumi ESC OIDC customization](#pulumi-esc-oidc-customization)
   - [Pulumi ESC Audit Logs](#pulumi-esc-audit-logs)
@@ -42,11 +42,11 @@ In collaboration with 1Password, we've launched the [1Password provider](/docs/e
 
 {{< video title="Pulumi ESC 1Password Provider Demo" src="https://www.pulumi.com/uploads/esc-1password-provider-demo.mp4" controls="false" autoplay="true" loop="true" >}}
 
-### Pulumi ESC Key-Value Table Editor
+### Pulumi ESC Table view
 
-We've rolled out the [Pulumi ESC Key-Value Table Editor](/blog/esc-key-value-table-editor-launch/), offering a novel, user-friendly interface for managing secrets and configurations. This addition complements the existing YAML-based editor, providing intuitive and familiar experiences for your workflows with secrets and configurations. Table Editor supports capabilities including CRUD operations for secrets and plaintext values, secret decryption, [environment imports](/docs/esc/environments/imports/), variable projections, and [interpolations](/docs/esc/environments/working-with-environments/#interpolating-values).
+We've rolled out the [Pulumi ESC Table view](/blog/esc-key-value-table-editor-launch/), offering a novel, user-friendly interface for managing secrets and configurations. This addition complements the existing YAML-based editor, providing intuitive and familiar experiences for your workflows with secrets and configurations. Table Editor supports capabilities including CRUD operations for secrets and plaintext values, secret decryption, [environment imports](/docs/esc/environments/imports/), variable projections, and [interpolations](/docs/esc/environments/working-with-environments/#interpolating-values).
 
-![Key-Value Table Editor](/blog/esc-key-value-table-editor-launch/esc-key-value-table-editor.png)
+![Table view](/blog/esc-key-value-table-editor-launch/esc-key-value-table-editor.png)
 
 ### Pulumi ESC YAML Code Editor Enhancements
 

content/docs/esc/get-started/store-and-retrieve-secrets.md

@@ -26,15 +26,15 @@ values:
 
 You can store and retrieve values in an environment via one of the following methods:
 
-- the Pulumi Cloud console Editor view
+- the Pulumi Cloud console Document view
 - the Pulumi Cloud console Table view
 - the ESC CLI
 
-## Store Environment Values
+## Store Environment values
 
-### Store via the Editor view
+### Store via the document view
 
-To store values in your environment using the Editor view, first click on the name of the environment to open it. You will be presented with a split pane view. The left side is the YAML-based code editor view, and this is where you will write the definition of your environment configuration. The right side will show a preview of your configuration in JSON format.
+To store values in your environment using the Document view, first click on the name of the environment to open it. You will be presented with a split pane view. The left side is the YAML-based code document view, and this is where you will write the definition of your environment configuration. The right side will show a preview of your configuration in JSON format.
 
 ![Open environment in Pulumi ESC console](/docs/esc/assets/esc-open-env.png)
 
@@ -51,15 +51,15 @@ As shown above, you can specify that a value should be stored as a secret by usi
 
 {{< video title="Adding values to the environment in the Pulumi ESC console" src="https://www.pulumi.com/uploads/esc-add-env-values.mp4" autoplay="true" loop="true" >}}
 
-The **Environment preview** pane on the right hand side will then update to show your added configuration in JSON format. You will notice that the value of "myPassword" has been hidden from view in both the defintion and preview panes.
+The **Environment preview** pane on the right-hand side will then update to show your added configuration in JSON format. You will notice that the value of "myPassword" has been hidden from view in both the definition and preview panes.
 
 ### Store via the Table view
 
-To store values in your environment using the Editor view, first click on the name of the environment to open it. Then, at the top of the Editor view view, click the **Table view** button to switch the editor from the YAML view to the table view.
+To store values in your environment using the Document view, first click on the name of the environment to open it. From the **Editor** menu, click the **Table view** button to switch the editor from the document YAML view to the table view.
 
 {{< video title="Adding values to the environment in the Pulumi ESC console" src="https://www.pulumi.com/uploads/esc-open-env-table-view.mp4" autoplay="true" loop="true" >}}
 
-Next, under the **Configuration** section section, you will see fields labeled **Path** and **Value**. You will define your configuraton values using these fields. In the **Path** field, type in `myEnvironment`, and in the **Value** field, type in `development`. Then click **Done** and **Save**.
+Next, under the **Configuration** section, you will see fields labeled **Path** and **Value**. You will define your configuration values using these fields. In the **Path** field, type in `myEnvironment`, and in the **Value** field, type in `development`. Then click **Done** and **Save**.
 
 ![Adding values to the environment in the Pulumi ESC console](/docs/esc/assets/esc-add-env-values.png)
 
@@ -94,11 +94,11 @@ esc env edit <project-name>/<environment-name>
 
 Using this method enables you to add your configuration values in the same way that you would [via the console](/docs/esc/get-started/store-and-retrieve-secrets/#store-via-the-console).
 
-## Retrieve Environment Values
+## Retrieve Environment values
 
-### Retrieve via the Editor view
+### Retrieve via the Document view
 
-To retrieve values using the Editor view, scroll to the bottom of your environment page and click the **Open** button. This will return any statically defined plain-text values and definitions.
+To retrieve values using the Document view, click the **Open** button. This will return any statically defined plain-text values and definitions.
 
 ![Clicking the open button in the Pulumi ESC console](/docs/esc/assets/esc-open-environment.png)