docs: rename to Fastly Compute

Author: Jake Champion

CHANGELOG.md

@@ -766,7 +766,7 @@ addEventListener("fetch", event => {
 
 #### Object-store support
 
-This release adds support for Fastly [Object-store](https://developer.fastly.com/reference/api/services/resources/kv-store/), which is globally consistent key-value storage accessible across the Fastly Network. This makes it possible for your Compute@Edge application to read and write from Object-stores.
+This release adds support for Fastly [Object-store](https://developer.fastly.com/reference/api/services/resources/kv-store/), which is globally consistent key-value storage accessible across the Fastly Network. This makes it possible for your Fastly Compute application to read and write from Object-stores.
 
 We've added two classes, `ObjectStore`, and `ObjectStoreEntry`. `ObjectStore` is used to interact with a particular Object-store and `ObjectStoreEntry` is a particular value within an Object-store. We've made `ObjectStoreEntry` have a similar API as `Response` to make it simpler to read and write from Object-stores. I.e. `ObjectStoreEntry` has a `body` property which is a `ReadableStream` and has `arrayBuffer`/`json`/`text` methods - just like `Response`.
 
@@ -901,7 +901,7 @@ console.log(request); // outputs `Request: {method: POST, url: https://www.fastl
 ### Added
 
 - Updated the js-compute-runtime to `0.2.2` (Which includes fixes to geoip, a way to get environment variables, improves debugging of exceptions in the request handler, and other updates)
-- Added the `Env` namespace for accessing Fastly C@E environment variables.
+- Added the `Env` namespace for accessing Fastly Compute environment variables.
 
 ## 0.2.0 (2021-08-31)
 
@@ -926,5 +926,5 @@ console.log(request); // outputs `Request: {method: POST, url: https://www.fastl
 ### Added
 
 - Initial Release
-- Includes TypeScript type definitions for Compute@Edge flavored ServiceWorkers APIs
+- Includes TypeScript type definitions for Fastly Compute flavored ServiceWorkers APIs
 - Also includes the `js-compute-runtime` CLI for bundling JavaScript applications

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing to the JS Compute Runtime
 
 First off thank you for wanting to contribute to making the JS Compute Runtime better! We
-appreciate you taking time to improve the Compute@Edge experience for developers
+appreciate you taking time to improve the Fastly Compute experience for developers
 everywhere. There are many ways you can contribute that include but aren't
 limited to documentation, opening issues, issue triage, and code contributions.
 We'll cover some of the ways you can contribute below, but if you don't see

DEVELOPMENT.md

@@ -1,8 +1,8 @@
-# Fastly Compute@Edge JS Runtime
+# Fastly Compute JS Runtime
 
-The JS Compute Runtime for Fastly's [Compute@Edge platform](https://www.fastly.com/products/edge-compute/serverless) provides the environment JavaScript is executed in when using the [Compute@Edge JavaScript SDK](https://www.npmjs.com/package/@fastly/js-compute).
+The JS Compute Runtime for Fastly's [Compute platform](https://www.fastly.com/products/edge-compute/serverless) provides the environment JavaScript is executed in when using the [Fastly Compute JavaScript SDK](https://www.npmjs.com/package/@fastly/js-compute).
 
-**Note**: If you just want to use JavaScript on the Compute@Edge Platform, we recommend using the JavaScript Starter Kits provided by the Fastly CLI tool. For more information please see the [JavaScript documentation on the Fastly Developer Hub](https://developer.fastly.com/learning/compute/javascript/).
+**Note**: If you just want to use JavaScript on the Fastly Compute Platform, we recommend using the JavaScript Starter Kits provided by the Fastly CLI tool. For more information please see the [JavaScript documentation on the Fastly Developer Hub](https://developer.fastly.com/learning/compute/javascript/).
 
 ## Working with the JS Compute Runtime source
 
@@ -72,6 +72,6 @@ To run an end-to-end test which builds and deploys an application to fastly:
 ## Testing a Dev Release
 :warning:	**You should not use this for production workloads!!!!!!!!**
 
-Dev builds are released before production releases to allow for further testing. These are not released upstream to NPM, however you can acquire them from the [Releases](https://github.com/fastly/js-compute-runtime/releases/) section. Download the runtime for your platform, extract the executable and place it in the /node_modules/@fastly/js-compute/bin/PLATFORM folder of your Compute@Edge project. Then you can use the normal [Fastly CLI](https://github.com/fastly/cli) to build your service. 
+Dev builds are released before production releases to allow for further testing. These are not released upstream to NPM, however you can acquire them from the [Releases](https://github.com/fastly/js-compute-runtime/releases/) section. Download the runtime for your platform, extract the executable and place it in the /node_modules/@fastly/js-compute/bin/PLATFORM folder of your Fastly Compute project. Then you can use the normal [Fastly CLI](https://github.com/fastly/cli) to build your service. 
 
 Please submit an [issue](https://github.com/fastly/js-compute-runtime/issues) if you find any problems during testing.

README.md

@@ -2,13 +2,13 @@
 
 ![npm version](https://img.shields.io/npm/v/@fastly/js-compute) ![npm downloads per month](https://img.shields.io/npm/dm/@fastly/js-compute)
 
-JavaScript SDK and CLI for building JavaScript applications on Fastly's [Compute@Edge](https://www.fastly.com/products/edge-compute/serverless).
+JavaScript SDK and CLI for building JavaScript applications on [Fastly Compute](https://www.fastly.com/products/edge-compute/serverless).
 
 ## Getting Started
 
-We recommend using the [Fastly CLI](https://github.com/fastly/cli) to create, build, and deploy JavaScript Compute@Edge services, as [described on the Fastly Developer Hub](https://developer.fastly.com/learning/compute/).
+We recommend using the [Fastly CLI](https://github.com/fastly/cli) to create, build, and deploy JavaScript Fastly Compute services, as [described on the Fastly Developer Hub](https://developer.fastly.com/learning/compute/).
 
-[Detailed documentation for JavaScript Compute@Edge services](https://developer.fastly.com/learning/compute/javascript/) is also available on Fastly Developer Hub.
+[Detailed documentation for JavaScript Fastly Compute services](https://developer.fastly.com/learning/compute/javascript/) is also available on Fastly Developer Hub.
 
 ## Usage
 

documentation/README.md

@@ -30,4 +30,4 @@ This command generates static content into the `build` directory and can be serv
 $ yarn deploy
 ```
 
-This command will run `yarn build` and then will upload the website to Fastly KV Store and deploy the application to Fastly Compute@Edge.
+This command will run `yarn build` and then will upload the website to Fastly KV Store and deploy the application to Fastly Compute.

documentation/app/fastly.toml

@@ -1,4 +1,4 @@
-# This file describes a Fastly Compute@Edge package. To learn more visit:
+# This file describes a Fastly Compute package. To learn more visit:
 # https://developer.fastly.com/reference/fastly-toml/
 
 authors = ["[email protected]"]

documentation/docs/fastly:backend/Backend/Backend.mdx

@@ -8,7 +8,7 @@ import {Fiddle} from '@site/src/components/fiddle';
 
 # `Backend()`
 
-The **`Backend` constructor** lets you dynamically create new [Fastly Backends](https://developer.fastly.com/reference/api/services/backend/) for your Compute@Edge service.
+The **`Backend` constructor** lets you dynamically create new [Fastly Backends](https://developer.fastly.com/reference/api/services/backend/) for your Fastly Compute service.
 
 Dynamically creating new [Fastly Backends](https://developer.fastly.com/reference/api/services/backend/) is disabled by default for Fastly Services. Please contact [Fastly Support](https://support.fastly.com/hc/requests/new?ticket_form_id=360000269711) to request the feature be enabled on the Fastly Services which require Dynamic Backends.
 

documentation/docs/fastly:env/env.mdx

@@ -10,7 +10,7 @@ import {Fiddle} from '@site/src/components/fiddle';
 
 The **`env()`** function returns the value for the provided environment variable name.
 
-For a list of available environment variables, see the [Fastly Developer Hub for C@E Environment Variables](https://developer.fastly.com/reference/compute/ecp-env/)
+For a list of available environment variables, see the [Fastly Developer Hub for Compute Environment Variables](https://developer.fastly.com/reference/compute/ecp-env/)
 
 >**Note**: The environment variables can only be retrieved when processing requests, not during build-time initialization.
 

documentation/docs/fastly:experimental/allowDynamicBackends.mdx

@@ -8,7 +8,7 @@ import {Fiddle} from '@site/src/components/fiddle';
 
 # allowDynamicBackends
 
-The **`allowDynamicBackends()`** function is used to control whether or not Dynamic Backends should be allowed within this Compute@Edge Service.
+The **`allowDynamicBackends()`** function is used to control whether or not Dynamic Backends should be allowed within this Fastly Compute Service.
 
 By default, Dynamic Backends are disabled within a JavaScript application as it can be a potential avenue for third-party JavaScript code to send requests, potentially including sensitive/secret data,  off to destinations that the JavaScript project was not intending, which could be a security issue.
 

documentation/docs/fastly:experimental/includeBytes.mdx

@@ -19,7 +19,7 @@ includeBytes(path)
 ### Parameters
 
 - `path` _: string_
-  - The path to include, relative to the Compute@Edge application's top-level directory during build-time initialization.
+  - The path to include, relative to the Fastly Compute application's top-level directory during build-time initialization.
 
 ### Return value