paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 19 Packages Projects Releases Wiki Activity

docs: fix typos in the documentation (#2633)

Browse Source
This commit is contained in:
Navaneeth Suresh
2020-09-28 16:48:40 +05:30
committed by GitHub
parent 17c30eaf3e
commit e7686833fd
25 changed files with 46 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plugins/index.md
+1 -1
View File
@@ -21,7 +21,7 @@ To create a plugin, follow the steps outlined [here](create-a-plugin.md).
## Suggesting a plugin
If you start developing a plugin that you aim to release as open source, we
suggest that you create a new
suggest that you create a
[new Issue](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
This helps the community know what plugins are in development.
docs/plugins/structure-of-a-plugin.md
+1 -1
View File
@@ -84,7 +84,7 @@ structure our plugins. There are usually one or multiple page components and
next to them you can split up the UI in as many components as you feel like.
We have the `ExamplePage` to show an example Backstage page component. The
`ExampleFetchComponent` show cases the common task of making an async request to
`ExampleFetchComponent` showcases the common task of making an async request to
a public API and plot the response data in a table using Material-UI components.
You may tweak these components, rename them and/or replace them completely.
docs/plugins/testing.md
+3 -3
View File
@@ -32,7 +32,7 @@ working on.
## Naming Test Files
Tests should be name `[filename].test.js`.
Tests should be named `[filename].test.js`.
For example, the tests for **`Link.js`** exist in the file **`Link.test.js`**.
@@ -54,7 +54,7 @@ TODO.
# Writing Unit Tests
The following principles are good guides to determining if you are writing high
The following principles are good guides for determining if you are writing high
quality frontend unit tests.
## Bad Unit Test Principle
@@ -170,7 +170,7 @@ input changes
component is mounted, just that it is mounted in response to the input.
✓ **Fulfills Scalability Principle**: If we decide to refactor the entire way
the loading indicator is displayed the test still works without touching it.
the loading indicator has displayed the test still works without touching it.
✓ **Fulfills Broken Functionality Principle**: this test verifies the
functionality (displaying an indicator) is working, rather than how it is