diff --git a/service-catalog/gcp-backup/README.md b/service-catalog/gcp-backup/README.md
index c633ff3..2956dde 100644
--- a/service-catalog/gcp-backup/README.md
+++ b/service-catalog/gcp-backup/README.md
@@ -109,18 +109,10 @@ No. [Multi-region](https://cloud.google.com/storage/docs/availability-durability
 It's the same region where the AWS S3 buckets are located. In this way, we reduce the latency of the transfer job.
 Also, the cost calculator indicates that this regions has a "Low CO2" and it's among the cheapest regions.
 
-### Why GCP? 🤌
+#### Why GCP?
 
-Both the Rust Foundation and the Rust project have a good working relationship with Google, and it is where the Rust Foundation's Security Initiative hosts its infrastructure. Due to the good collaboration with Google, we expect that we can cover the costs of the backup with credits provided by GCP.
-
-## Unresolved questions
-
-Issues that need to be resolved before the backup is set up:
-
-- We will use the billing information of the Rust Foundation. Can we cover the cost with the GCP credits we currently have or are they bound to just one account?
-- Should we contact Google before setting the account so that they can cover the cost?
-- We are backing up public data of the crates-io database (`db-dump` in the `crates-io` bucket). Should we also backup private data of the crates-io database? The concern here is that it contains private information, such as API token.
-- Should we backup the `crates-io-index` even though we can restore it from `db-dump`? Pro: the restore phase is faster because we need to manually restore the index and copy the file. Cons: the backup costs a bit more.
+Both the Rust Foundation and the Rust project have a good working relationship with Google, and it is where the Rust Foundation's Security Initiative hosts its infrastructure.
+Due to the good collaboration with Google, we expect that we can cover the costs of the backup with credits provided by Google.
 
 [infra-admins]: https://github.com/rust-lang/team/blob/master/teams/infra-admins.toml
 [threat model]: https://docs.google.com/document/d/10Qlf8lk7VbpWhA0wHqJj4syYuUVr8rkGVM-k2qkb0QE