diff --git a/microsite/blog/2021-06-24-announcing-backstage-search-platform.mdx b/microsite/blog/2021-06-24-announcing-backstage-search-platform.mdx
index 89692c57bc..bb30a3b9ec 100644
--- a/microsite/blog/2021-06-24-announcing-backstage-search-platform.mdx
+++ b/microsite/blog/2021-06-24-announcing-backstage-search-platform.mdx
@@ -80,7 +80,7 @@ That's why we have put effort into making your search page experience composable
 
 A good example of the level of customization the platform allows is how list items are displayed in search results. A search result component can be a list, this list can consist of different list items (search results returned from the search engine) — but these list items could look different depending on what the search result returns in terms of its fields.
 
-Let’s say that for an entity returned from the software catalog maybe the most important information to show is the name, while a result returned from the TechDocs plugin should maybe show the text content as the most important information. This can be customized by creating `<CustomResultListItem />` components (like TechDocsResultListItem or CatalogResultListItem or whatever list item component you want) and configuring them in the app.
+Let’s say that for an entity returned from the software catalog maybe the most important information to show is the name, while a result returned from the TechDocs plugin should maybe show the text content as the most important information. This can be customized by creating `<CustomResultListItem />` components (like `TechDocsResultListItem` or `CatalogResultListItem` or whatever list item component you want) and configuring them in the app.
 
 If there is no need to customize your search result list items, the `<DefaultResultListItem />` component is there for you to reuse.