some more small doc fixes

Signed-off-by: Fredrik Adelöw <freben@gmail.com>

docs/features/search/declarative-integration.md

@@ -161,13 +161,13 @@ The `createSearchResultItemExtension` function returns a Backstage's extension r
 
 In this object, you can see exactly what will happen once the custom extension is installed:
 
-- **[1] $$type**: declares that the object represents an extension;
-- **[2] id**: Is a unique identification for the extension, the `plugin.search.result.item.techdocs` is the key used to configure the extension in the `app-config.yaml` file;
-- **[3] at**: It represents the extension attachment point, so the value `plugin.search.page/items` says that the `TechDocs`'s search result item output will be injected as input on the "items" attachment expected by the search page extension;
-- **[4] inputs**: in this case is an empty object because this extension doesn't expect inputs;
-- **[5] output**: Object representing the artifact produced by the `TechDocs` result item extension, on the example, it is a react component reference;
-- **[6] configSchema**: represents the `TechDocs` search result item configuration definition, this is the same schema that adopters will use for customizing the extension via `app-config.yaml` file;
-- **[7] disable**: Says that the result item extension will be enable by default when the `TechDocs` plugin is installed in the app.
+- **[1] `$$type`**: declares that the object represents an extension;
+- **[2] `id`**: Is a unique identification for the extension, the `plugin.search.result.item.techdocs` is the key used to configure the extension in the `app-config.yaml` file;
+- **[3] `at`**: It represents the extension attachment point, so the value `plugin.search.page/items` says that the `TechDocs`'s search result item output will be injected as input on the "items" attachment expected by the search page extension;
+- **[4] `inputs`**: in this case is an empty object because this extension doesn't expect inputs;
+- **[5] `output`**: Object representing the artifact produced by the `TechDocs` result item extension, on the example, it is a react component reference;
+- **[6] `configSchema`**: represents the `TechDocs` search result item configuration definition, this is the same schema that adopters will use for customizing the extension via `app-config.yaml` file;
+- **[7] `disable`**: Says that the result item extension will be enable by default when the `TechDocs` plugin is installed in the app.
 
 To complete the development cycle for creating a custom search result item extension, we should provide the extension via `TechDocs` plugin:
 

docs/features/software-catalog/external-integrations.md

@@ -775,7 +775,7 @@ sent. Luckily many external systems provide ETag support to check for changes
 which usually doesn't count towards the quota and saves resources both
 internally and externally.
 
-The catalog has built in support for leveraging ETags when refreshing external
+The catalog has built in support for leveraging `ETag`s when refreshing external
 locations in GitHub. This example aims to demonstrate how to add the same
 behavior for `system-x` that we implemented earlier.
 

docs/features/software-catalog/index.md

@@ -126,7 +126,7 @@ _starring_ of components:
 The software catalog is a great way to organize the infrastructure tools you use
 to manage the software. This is how Backstage creates one developer portal for
 all your tools. Rather than asking teams to jump between different
-infrastructure UIs (and incurring additional cognitive overhead each time they
+infrastructure user interfaces (and incurring additional cognitive overhead each time they
 make a context switch), most of these tools can be organized around the entities
 in the catalog.
 

docs/features/software-catalog/life-of-an-entity.md

@@ -133,7 +133,7 @@ the order of registration depends on the order in which the modules are loaded
 by the framework.
 
 It's possible to customize the order of the processors by modifying the
-`catalog.processors.<processorName>.priority` configuration option.
+`catalog.processorOptions.<processorName>.priority` configuration option.
 The default priority is `20`, and lower value means that the processor runs earlier.
 
 :::