Skip to content

Commit ae038c1

Browse files
committed
chore(readme): fix incorrect master->main changes
1 parent 86d2487 commit ae038c1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ Cloud Graph lets you **Know your cloud** in 5 minutes. Built and maintained with
8585
- [McKinsey](https://www.mckinsey.com/)
8686
- [Pulumi](https://www.pulumi.com/)
8787
- [Siemens](https://www.siemens.com/)
88-
- [mainCard](https://www.maincard.us/en-us.html)
88+
- [MasterCard](https://www.mastercard.us/en-us.html)
8989

9090
\*\* usage does not imply endorsement
9191

@@ -107,7 +107,7 @@ Anyone familiar with the CSPs knows that service APIs are almost always split in
107107

108108
<br />
109109

110-
While a mainpiece of datacenter architecture, this choice of hundreds of services and configuration options put the burden of knowledge on how to properly use these services squarely on us engineers. As a result, we find ourselves having to constantly stay up to date and learn about all the service offerings or new changes. This takes a significant amount of time and mental energy. As developers, it can be difficult, time-consuming, and frustrating to use the AWS CLI to make 5 different API calls to describe, as an example, an AWS ECS cluster, its services, task definitions, tasks, container definitions, etc. We often find ourselves lost in documentation and having to use half a dozen of APIs to get answers to questions like "What exactly is running in this VPC?"
110+
While a masterpiece of datacenter architecture, this choice of hundreds of services and configuration options put the burden of knowledge on how to properly use these services squarely on us engineers. As a result, we find ourselves having to constantly stay up to date and learn about all the service offerings or new changes. This takes a significant amount of time and mental energy. As developers, it can be difficult, time-consuming, and frustrating to use the AWS CLI to make 5 different API calls to describe, as an example, an AWS ECS cluster, its services, task definitions, tasks, container definitions, etc. We often find ourselves lost in documentation and having to use half a dozen of APIs to get answers to questions like "What exactly is running in this VPC?"
111111

112112
<br />
113113

0 commit comments

Comments
 (0)