DEVLIB-1233: Rename Compute@Edge to Compute

Author: doramatadora

README.md

@@ -2,9 +2,9 @@
 
 [![Deploy to Fastly](https://deploy.edgecompute.app/button)](https://deploy.edgecompute.app/deploy)
 
-Speed up your websites with a Compute@Edge environment that demonstrates serving content from a static bucket, redirects, security and performance headers, and a 404 page.
+Speed up your websites with a Fastly Compute environment that demonstrates serving content from a static bucket, redirects, security and performance headers, and a 404 page.
 
-**For more details about this and other starter kits for Compute@Edge, see the [Fastly developer hub](https://developer.fastly.com/solutions/starters)**
+**For more details about this and other starter kits for Compute, see the [Fastly developer hub](https://developer.fastly.com/solutions/starters)**
 
 ## Features
 
@@ -59,7 +59,7 @@ If your bucket requires authentication, you will need to create an [edge diction
 
 This starter is feature-packed, and requires some extra dependencies on top of the [`fastly`](https://docs.rs/fastly) crate to handle signing requests for S3/GCS. If you are using a public bucket for your origin, these dependencies will not be included.
 
-This starter includes implementations of common patterns explained in our [using Compute@Edge](/learning/compute/rust/) and [VCL migration](/learning/compute/migrate/) guides. Any of the code you see here can be modified or built upon to suit your project's needs.
+This starter includes implementations of common patterns explained in our [using Compute](/learning/compute/rust/) and [VCL migration](/learning/compute/migrate/) guides. Any of the code you see here can be modified or built upon to suit your project's needs.
 
 To learn more about how Fastly communicates with your bucket host, read the [Integrating third party services as backends](https://developer.fastly.com/learning/integrations/backends/) guide. This is based on a VCL service, but you can utilise many of the same patterns with the help of the [VCL migration](/learning/compute/migrate/) guide.
 

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]>"]

src/main.rs

@@ -1,4 +1,4 @@
-//! Compute@Edge static content starter kit program.
+//! Compute static content starter kit program.
 
 mod config;
 
@@ -72,7 +72,7 @@ fn main(mut req: Request) -> Result<Response, Error> {
     // Assign the path to a variable to be used later.
     let original_path = req.get_path().to_owned();
 
-    // Set the `Host` header to the bucket host rather than our C@E endpoint.
+    // Set the `Host` header to the bucket host rather than our Compute endpoint.
     req.set_header(
         header::HOST,
         format!("{}.{}", config::BUCKET_NAME, config::BUCKET_HOST),
@@ -162,7 +162,7 @@ fn main(mut req: Request) -> Result<Response, Error> {
 
     // Compress assets.
     if original_path.starts_with("/assets/") {
-        // C@E services currently run behind h2o (https://github.com/h2o/h2o)
+        // Compute services currently run behind h2o (https://github.com/h2o/h2o)
         // This header will enable compression on the downstream message in h2o
         beresp.set_header("X-Compress-Hint", "on");
     }