diff --git a/docs/features/software-catalog/descriptor-format.md b/docs/features/software-catalog/descriptor-format.md
index 3a1db235a0..62ac9da8d8 100644
--- a/docs/features/software-catalog/descriptor-format.md
+++ b/docs/features/software-catalog/descriptor-format.md
@@ -12,7 +12,7 @@ This both applies to objects given to and returned from the software catalog
 API, as well as to the descriptor files that the software catalog can ingest
 natively. In the API request/response cycle, a JSON representation is used,
 while the descriptor files are on YAML format to be more easily maintainable by
-humans. However, the structure and semantics is the same in both cases.
+humans. However, the structure and semantics are the same in both cases.
 
 Although it's possible to name catalog entity descriptor files however you wish,
 we recommend that you name them `catalog-info.yaml`.
@@ -113,7 +113,7 @@ data.
 Backstage specific entities have an `apiVersion` that is prefixed with
 `backstage.io/`, to distinguish them from other types of object that share the
 same type of structure. This may be relevant when co-hosting these
-specifications with e.g. kubernetes object manifests, or when an organization
+specifications with e.g. Kubernetes object manifests, or when an organization
 adds their own specific kinds of entity to the catalog.
 
 Early versions of the catalog will be using alpha/beta versions, e.g.