From 983d3d44bfe657638625915b891cfe2c0729f4bd Mon Sep 17 00:00:00 2001 From: AlleyWei <64219471+AlleyWei@users.noreply.github.com> Date: Fri, 21 May 2021 08:04:50 -0400 Subject: [PATCH] Update microsite/blog/2021-05-20-adopting-backstage.md Co-authored-by: Tim --- microsite/blog/2021-05-20-adopting-backstage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/microsite/blog/2021-05-20-adopting-backstage.md b/microsite/blog/2021-05-20-adopting-backstage.md index 8b3e9d403a..1aad5ce0bd 100644 --- a/microsite/blog/2021-05-20-adopting-backstage.md +++ b/microsite/blog/2021-05-20-adopting-backstage.md @@ -127,7 +127,7 @@ Integrating infrastructure of this size and complexity can seem overwhelming. It **Recommendation — Create, then manage, then explore:** - The fastest way to bring change to your ecosystem is to start at the beginning of the chain with Backstage Software Templates. -- With every new component created with your templates, you’re establishing best practices and rewarding your developers with a streamlined experience focussed on their needs — all the while building up your new service catalog. +- With every new component created with your templates, you’re establishing best practices and rewarding your developers with a streamlined experience focused on their needs — all the while building up your new service catalog. - The more the templates ease the process of starting up a project, the more your engineers will adopt them, and the faster the other benefits of Backstage will build up, transforming productivity across your organization. ([That’s how we did it at Spotify](https://open.spotify.com/episode/7iuQ3ew1Wwpuiq6LbBKzCl).) ## More questions about adopting Backstage?