From f3f684fbb911ca6cd8d8d62ded0d8cc3084b235e Mon Sep 17 00:00:00 2001
From: 0xflotus <0xflotus@gmail.com>
Date: Tue, 7 Jul 2020 12:39:01 +0200
Subject: [PATCH] (docs): fixed small error (#1551)

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 983a8efea4..40f12f3b3e 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ For more information go to [backstage.io](https://backstage.io) or join our [Dis
 
 The Backstage Service Catalog — actually, a software catalog, since it includes more than just services — is a centralized system that keeps track of ownership and metadata for all the software in your ecosystem (services, websites, libraries, data pipelines, etc). The catalog is built around the concept of [metadata yaml files](https://github.com/spotify/backstage/blob/master/docs/architecture-decisions/adr002-default-catalog-file-format.md#format) stored together with the code, which are then harvested and visualized in Backstage.
 
-![servce-catalog](https://backstage.io/blog/assets/6/header.png)
+![service-catalog](https://backstage.io/blog/assets/6/header.png)
 
 We have also found that the service catalog is a great way to organise the infrastructure tools you use to manage the software as well. This is how Backstage creates one developer portal for all your tools. Rather than asking teams to jump between different infrastructure UI’s (and incurring additional cognitive overhead each time they make a context switch), most of these tools can be organised around the entities in the catalog.
 
@@ -82,7 +82,7 @@ yarn start # Start dev server, use --check to enable linting and type-checks
 
 The final `yarn start` command should open a local instance of Backstage in your browser, otherwise open one of the URLs printed in the terminal.
 
-And thats it! You are good to go 👍
+And that's it! You are good to go 👍
 
 ### Next step