Remove remaining erroneous instances of 'the Pulumi Cloud' (#15437)

Author: jkodroff

content/docs/iac/extending-pulumi/_index.md

@@ -62,7 +62,7 @@ Here's some quick rules-of-thumb for deciding whether to create a component or a
 
 ## Local vs Remote
 
-In our documentation we sometimes refer to things as being "local" vs "remote" (e.g. using a local package). This has to do with where the Pulumi Engine is running. When you run the `pulumi up` command via the CLI, the Pulumi Engine will run on the same machine. That engine loads and runs the plugins and interacts with the backend to manage state. In this mode, it is running *locally*, and therefore has access to the filesystem on that machine, and could load a plugin directly from a locally stored directory. However, when using Pulumi Deployments in the Pulumi Cloud, the Pulumi Engine is running in a virtual machine on our infrastructure. In that case, it is running "remotely".
+In our documentation we sometimes refer to things as being "local" vs "remote" (e.g. using a local package). This has to do with where the Pulumi Engine is running. When you run the `pulumi up` command via the CLI, the Pulumi Engine will run on the same machine. That engine loads and runs the plugins and interacts with the backend to manage state. In this mode, it is running *locally*, and therefore has access to the filesystem on that machine, and could load a plugin directly from a locally stored directory. However, when using Pulumi Deployments in Pulumi Cloud, the Pulumi Engine is running in a virtual machine on our infrastructure. In that case, it is running "remotely".
 
 This matters when we talk about components and providers because Pulumi Deployments might fail to load a plugin that doesn't exist in its environment. In order for Pulumi Deployments to access the plugin, it needs to be packaged and published to the Pulumi Registry, so that it can be downloaded at runtime. Or, in the case of components and dynamic providers, the code needs to be committed alongside your normal Pulumi program code, in the same Git repository.
 

content/docs/iac/get-started/azure/destroy-stack.md

@@ -15,7 +15,7 @@ Now that you've seen how to deploy changes to our program, let's clean up and te
 To destroy resources, run the following:
 
 ```bash
-$ pulumi destroy
+pulumi destroy
 ```
 
 You'll be prompted to make sure you really want to delete these resources. This can take a minute or two; Pulumi waits until all resources are shut down and deleted before it considers the destroy operation to be complete.
@@ -58,7 +58,7 @@ Duration: 53s
 ```
 
 To delete the stack itself, run [`pulumi stack rm`](/docs/cli/commands/pulumi_stack_rm). Note that this removes the stack
-entirely from the Pulumi Cloud, along with all of its update history.
+entirely from Pulumi Cloud, along with all of its update history.
 
 Congratulations! You've successfully provisioned some cloud resources using Pulumi. By completing this guide you have successfully:
 

content/docs/iac/get-started/kubernetes/destroy-stack.md

@@ -67,7 +67,7 @@ If you want to remove the stack completely, run `pulumi stack rm dev`.
 ```
 
 To delete the stack itself, run [`pulumi stack rm`](/docs/cli/commands/pulumi_stack_rm). Note that this removes the stack
-entirely from the Pulumi Cloud, along with all of its update history.
+entirely from Pulumi Cloud, along with all of its update history.
 
 ```bash
 $ pulumi stack rm

content/docs/iac/support/faq.md

@@ -49,7 +49,7 @@ Pulumi provides primitives so you can enforce your [secrets](/docs/concepts/secr
 
 ### How does Pulumi manage secrets?
 
-When you set a [configuration](/docs/concepts/config/) value, you may pass `--secret` to `pulumi config set` which causes the value to be encrypted so it can be safely persisted in `Pulumi.<stack-name>.yaml`. For every stack the Pulumi Cloud manages a unique encryption key, which it uses to encrypt secrets for that stack (and this is configurable to use your own custom secrets provider). Because a different key is used for each stack, encrypting the same value across two different stacks will lead to different encrypted strings being stored in the `Pulumi.<stack-name>.yaml` files. This also means that you cannot copy an encrypted value from one file to another using a text editor. Instead, you must use `pulumi config set`.
+When you set a [configuration](/docs/concepts/config/) value, you may pass `--secret` to `pulumi config set` which causes the value to be encrypted so it can be safely persisted in `Pulumi.<stack-name>.yaml`. For every stack Pulumi Cloud manages a unique encryption key, which it uses to encrypt secrets for that stack (and this is configurable to use your own custom secrets provider). Because a different key is used for each stack, encrypting the same value across two different stacks will lead to different encrypted strings being stored in the `Pulumi.<stack-name>.yaml` files. This also means that you cannot copy an encrypted value from one file to another using a text editor. Instead, you must use `pulumi config set`.
 
 When you run a preview, update or destroy, pulumi decrypts this data. It is plain text during the execution of your deployment, and any part of your Pulumi program may access it using the Pulumi config object.
 

content/docs/iac/support/troubleshooting.md

@@ -251,11 +251,11 @@ Full error example:
 error: could not load plugin for aws provider 'urn:pulumi:<stack_name>::pulumi-service::pulumi:providers:aws::default': no resource plugin 'aws-v0.16.2' found in the workspace or on your $PATH, install the plugin using \`pulumi plugin install resource aws v0.16.2\`
 ```
 
-### Cannot connect to the Pulumi Cloud
+### Cannot connect to Pulumi Cloud
 
-If your network blocks external traffic and you're using the Pulumi Cloud to manage your state, your security team may need the following details to allow the Pulumi CLI to connect to the Pulumi Cloud:
+If your network blocks external traffic and you're using Pulumi Cloud to manage your state, your security team may need the following details to allow the Pulumi CLI to connect to Pulumi Cloud:
 
-- The URL that the Pulumi CLI uses to connect to the Pulumi Cloud is `https://api.pulumi.com`. (It does not use `https://app.pulumi.com`, so if you want to view the console from a web browser, you will need to enable that as well.)
+- The URL that the Pulumi CLI uses to connect to Pulumi Cloud is `https://api.pulumi.com`. (It does not use `https://app.pulumi.com`, so if you want to view the console from a web browser, you will need to enable that as well.)
 - All access goes over HTTPS via port 443.
 
 ### Nothing happens due to a network proxy

content/docs/iac/using-pulumi/continuous-delivery/add-support-for-cicd-systems.md

@@ -1,7 +1,7 @@
 ---
 title_tag: "Add Support for CI/CD Systems"
 meta_desc: This guide walks you through how you can configure your CI/CD environment manually
-           to surface data in the Pulumi Cloud.
+           to surface data in Pulumi Cloud.
 title: Adding CI/CD support
 h1: Adding Pulumi support for CI/CD systems
 meta_image: /images/docs/meta-images/docs-meta.png
@@ -21,7 +21,7 @@ aliases:
 
 If the Pulumi CLI doesn't automatically detect your CI/CD system, this guide
 walks you through how you can configure your CI/CD environment manually
-to surface data in the Pulumi Cloud.
+to surface data in Pulumi Cloud.
 
 ## Overview
 
@@ -69,7 +69,7 @@ The `EnvVarsToDetect` is used by the `IsCI()` in [`systems.go`](https://github.c
 
 ### Detecting Additional Metadata About A CI Build
 
-A CI build could have been triggered by a PR or a push build. In this case, the linked PR number is useful so that the Pulumi Cloud can link to it. Note that the detection is done on a best-effort basis. We support linking to the following Git-based version control systems:
+A CI build could have been triggered by a PR or a push build. In this case, the linked PR number is useful so that Pulumi Cloud can link to it. Note that the detection is done on a best-effort basis. We support linking to the following Git-based version control systems:
 
 - Atlassian Bitbucket
 - Azure DevOps

content/docs/iac/using-pulumi/continuous-delivery/azure-devops.md

@@ -70,7 +70,7 @@ Install the Pulumi task from the [Visual Studio Marketplace](https://marketplace
 
 The task requires the use of a service connection, which allows the pipeline to connect to your Azure Subscription. The task also looks for the build variable `pulumi.access.token`, and automatically maps it to the environment variable `PULUMI_ACCESS_TOKEN`, that is used by the CLI for non-interactive logins. You may still use the `env` directive to map any other environment variables you wish to make available to your Pulumi app.
 
-You can obtain a [Pulumi access token](/docs/pulumi-cloud/accounts#access-tokens) from the Pulumi Cloud. Then use the task in your pipeline yaml.
+You can obtain a [Pulumi access token](/docs/pulumi-cloud/accounts#access-tokens) from Pulumi Cloud. Then use the task in your pipeline yaml.
 
 ```yaml
 # Lines omitted for brevity.

content/docs/iac/using-pulumi/continuous-delivery/github-actions.md

@@ -347,7 +347,7 @@ jobs:
 Now that you've got these two common workflows defined, you'll need to configure your
 secrets. Secrets are exposed as environment variables to the GitHub Actions runtime
 environment. Minimally, you'll need to supply a [Pulumi access token](/docs/pulumi-cloud/accounts#access-tokens)
-to allow the Pulumi CLI to communicate with the Pulumi Cloud on your behalf, and
+to allow the Pulumi CLI to communicate with Pulumi Cloud on your behalf, and
 you'll probably want to provide credentials for communicating with your cloud
 provider as well.
 
@@ -360,7 +360,7 @@ to your repo's **Settings** tab, where you'll find the new **Secrets** area:
 
 First, [create a new Pulumi Access Token](https://app.pulumi.com/account/tokens), then
 submit that token as a new secret named named `PULUMI_ACCESS_TOKEN`. This enables your
-GitHub Action to communicate with the Pulumi Cloud on your behalf.
+GitHub Action to communicate with Pulumi Cloud on your behalf.
 
 Next, add secrets for your cloud credentials, just as you did `PULUMI_ACCESS_TOKEN` above,
 based on your provider of choice. For example:
@@ -379,7 +379,7 @@ went as planned:
 ![Action Checks](/images/docs/reference/gh-actions-checks.png)
 
 Select the Logs pane to see the full output of the Pulumi CLI, along with the URL of your
-deployment on the Pulumi Cloud with more details:
+deployment on Pulumi Cloud with more details:
 
 ![Action Logs](/images/docs/reference/gh-actions-logs.png)
 
@@ -399,7 +399,7 @@ the GitHub Actions container directly.
 ### Pulumi GitHub App
 
 The [Pulumi GitHub App](/docs/using-pulumi/continuous-delivery/github-app/) is something you install on your
-GitHub organization. It allows the Pulumi Cloud to leave comments on Pull Requests.
+GitHub organization. It allows Pulumi Cloud to leave comments on Pull Requests.
 
 Once the Pulumi GitHub App is installed, when your GitHub Actions run Pulumi, a summary of
 any resource changes will be left on the Pull Request, as well as links to the Pulumi

content/docs/iac/using-pulumi/continuous-delivery/github-app.md

@@ -39,7 +39,7 @@ This provides even more detail about any resource changes, including the full up
 ## Installation and Configuration
 
 {{% notes type="warning" %}}
-While the app can be installed via GitHub, it **must be installed through the Pulumi Cloud** using the steps below to ensure correct setup. Installing through the Pulumi Cloud ensures we have a connection from Pulumi to your GitHub user or organization.
+While the app can be installed via GitHub, it **must be installed through Pulumi Cloud** using the steps below to ensure correct setup. Installing through Pulumi Cloud ensures we have a connection from Pulumi to your GitHub user or organization.
 {{% /notes %}}
 
 {{% notes type="info" %}}

content/docs/iac/using-pulumi/continuous-delivery/harness.md

@@ -718,11 +718,8 @@ Following these best practices will help ensure reliable, secure, and maintainab
 When integrating Harness with Pulumi, you may encounter some common issues. Here are solutions to the most frequently encountered problems:
 
 - **Authentication Failures**: Ensure all required secrets are properly configured in Harness or Pulumi ESC.
-
-- **Stack Not Found**: Verify stack names and ensure stacks exist in the Pulumi Cloud.
-
+- **Stack Not Found**: Verify stack names and ensure stacks exist in Pulumi Cloud.
 - **Resource Conflicts**: Use `pulumi refresh` to sync state with actual cloud resources.
-
 - **Pipeline Timeouts**: Increase timeout values for long-running infrastructure deployments.
 
 For additional troubleshooting, see our [CI/CD troubleshooting guide](/docs/iac/using-pulumi/continuous-delivery/troubleshooting-guide).