diff --git a/packages/cli/templates/default-backend-plugin/dev/index.ts.hbs b/packages/cli/templates/default-backend-plugin/dev/index.ts.hbs
index 07dc091083..ce1d2919c9 100644
--- a/packages/cli/templates/default-backend-plugin/dev/index.ts.hbs
+++ b/packages/cli/templates/default-backend-plugin/dev/index.ts.hbs
@@ -7,7 +7,7 @@ import { catalogServiceMock } from '@backstage/plugin-catalog-node/testUtils';
 // minimal backend that can use both real and mocked plugins and services.
 //
 // Start up the backend by running `yarn start` in the package directory.
-// It's it's up and running, try out the following requests:
+// Once it's up and running, try out the following requests:
 //
 // Create a new todo item, standalone or for the sample component:
 //
diff --git a/packages/cli/templates/default-backend-plugin/src/plugin.test.ts.hbs b/packages/cli/templates/default-backend-plugin/src/plugin.test.ts.hbs
index cd4b9fc438..b6f387383e 100644
--- a/packages/cli/templates/default-backend-plugin/src/plugin.test.ts.hbs
+++ b/packages/cli/templates/default-backend-plugin/src/plugin.test.ts.hbs
@@ -9,7 +9,7 @@ import { catalogServiceMock } from '@backstage/plugin-catalog-node/testUtils';
 // TEMPLATE NOTE:
 // Plugin tests are integration tests for your plugin, ensuring that all pieces
 // work together end-to-end. You can still mock injected backend services
-// however, just like anyway that installs your plugin might replace the
+// however, just like anyone who installs your plugin might replace the
 // services with their own implementations.
 describe('plugin', () => {
   it('should create and read TODO items', async () => {