docs: fix typos in the documentation (#2633)

2020-09-28 16:48:40 +05:30
parent 17c30eaf3e
commit e7686833fd
25 changed files with 46 additions and 46 deletions
@@ -22,7 +22,7 @@ This ADR describes the default format of these descriptor files.

 ### Inspiration

-Internally at Spotify, a home grown software catalog system is used heavily and
+Internally at Spotify, a homegrown software catalog system is used heavily and
 forms a core part of Backstage and other important pieces of the infrastructure.
 The user experience, learnings and certain pieces of metadata from that catalog
 are being carried over to the open source effort.
@@ -40,7 +40,7 @@ triggers from the version control system, etc.

 Each file describes one or more entities in accordance with the
 [Backstage System Model](https://github.com/spotify/backstage/issues/390). All
-of these entities have a common stucture and nomenclature, and they are stored
+of these entities have a common structure and nomenclature, and they are stored
 in the software catalog from which they then can be queried.

 Entities have distinct names, and they may reference each other by those names.
@@ -44,7 +44,7 @@ A summary:
  name each.

 Using named exports helps prevent needing to rename symbols, which has myriad
-benefts. A few are:
+benefits. A few are:

 - IDE tools like "Find All References" and "Go To Definition" function
 - Manual codebase searching ("grep", etc) is easier with a unique symbol
@@ -22,7 +22,7 @@ or
 We currently do not use any pattern for how to structure exports. There is a mix
 of package-level re-exports deep into the directory tree, shallow re-exports for
 each directory, exports using `*` and explicit lists of each symbol, etc. The
-mix and lack of predictability makes it difficult to reason about the boundaries
+mix and lack of predictability make it difficult to reason about the boundaries
 of a module, and for example knowing whether it is safe to export a symbol in a
 given file.

@@ -13,7 +13,7 @@ with next to no benefits in combination with a few downsides.
 The main reasons were:

 - **children props** were implicitly added
- **Generic Type** were not supported on children
+- **Generic Type** was not supported on children

 Read more about the removal in
 [this PR](https://github.com/facebook/create-react-app/pull/8177).
@@ -11,7 +11,7 @@ tests, unit tests to e2e tests always have their own implementation of mocking
 these requests. There's been traction in the outer community towards using this
 library to mock network requests by using an express style declaration for
 routes. react-testing-library suggests using this library instead of mocking
-fetch directly wether this be in a browser or in node.
+fetch directly whether this be in a browser or in node.

 https://github.com/mswjs/msw