From a7554fdbdbc80d8b12e4adef2ac894f18963ba33 Mon Sep 17 00:00:00 2001 From: Rigin Oommen Date: Mon, 22 Jul 2024 13:04:52 +0530 Subject: [PATCH] fix(typo): corrected spelling error in the readme (#93) Signed-off-by: Rigin Oommen --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 936d111..549c9cd 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ ## ![Score](/docs/images/logo.svg) The Score Specification -Score is an open-soure workload specification designed to simplify development for cloud-native developers. The specification enables you to describe your workload's configuration in a vendor-neutral way, eliminating the need for tooling-specific syntax from platforms such as Docker Compose or Kubernetes. By leveraging familiar concepts and semantics, defining a workload’s configuration becomes as simple as stating, “I want a database of type X and an event queue of type Y to accompany my workload”. +Score is an open-source workload specification designed to simplify development for cloud-native developers. The specification enables you to describe your workload's configuration in a vendor-neutral way, eliminating the need for tooling-specific syntax from platforms such as Docker Compose or Kubernetes. By leveraging familiar concepts and semantics, defining a workload’s configuration becomes as simple as stating, “I want a database of type X and an event queue of type Y to accompany my workload”. Below is an example of a Score specification describing a web server that queries a Postgres database on each request. Typically, this file is saved alongside the workload's source code in version control.