AWS may have arbitrary names that don't follow any patterns, and Azure may have names that are grandiose, but at least you know with both of those clouds that they will always capitalize the name of all their service/product in documentation. There's no confusion if they are talking about a load balancer in the abstract, or their specific managed offerings.
- Cloud Logging - stores logs
- Google Compute Engine - VMs, compute
- Cloud Monitoring - stores metrics, monitors stuff
- Cloud Storage - stores stuff
- Google Kubernetes Engine - runs Kubernetes clusters
- BigQuery - runs multi-billion row queries with ease
- Cloud Functions - FaaS run time
Now sure, Cloud Spanner is a DB, without DB in the name, so you'll have to read the docs for a few seconds, but let's compare that to Cognito (brains?), X-ray (medical imaging?), Kinesis (something to do with mitosis?).
Take the example of "GKE Ingress for HTTP(S) Load Balancing." It's overly generic and doesn't tell you at a quick glance whether you are buying a specific managed load balancer or running something yourself, and whether you are using basic exits to the public internet or buying into a global network accelerator.