@@ -42,7 +42,7 @@ There are 3 ways to add components to the catalog:
|
||||
### Manually register components
|
||||
|
||||
Users can register new components by going to `/create` and clicking the
|
||||
**REGSITER EXISTING COMPONENT** button:
|
||||
**REGISTER EXISTING COMPONENT** button:
|
||||
|
||||

|
||||
|
||||
@@ -78,7 +78,7 @@ them, and do so using their normal Git workflow.
|
||||
Once the change has been merged, Backstage will automatically show the updated
|
||||
metadata in the service catalog after a short while.
|
||||
|
||||
## Finding software in the catlog
|
||||
## Finding software in the catalog
|
||||
|
||||
By default the service catalog shows components owned by the team of the logged
|
||||
in user. But you can also switch to _All_ to see all the components across your
|
||||
|
||||
@@ -5,7 +5,7 @@ software and resources leads to a better Backstage experience.
|
||||
|
||||
_This description originates from
|
||||
[this RFC](https://github.com/spotify/backstage/issues/390). Note that some of
|
||||
the concpets are not yet supported in Backstage._
|
||||
the concepts are not yet supported in Backstage._
|
||||
|
||||
## Concepts
|
||||
|
||||
|
||||
Reference in New Issue
Block a user