Skip to content

typo fixes & internal link #292

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 13, 2022
Merged

typo fixes & internal link #292

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/topics/best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,9 @@ all are required.
to write your own (see the link below to learn more about choosing a license), and our recommended
practice is to choose a license that allows for re-use by anyone, e.g. [Apache 2.0][apache-license].

If possible, the license should be specified wit its corresponding [SPDX identifier][spdx].
If possible, the license should be specified with its corresponding [SPDX identifier][spdx].
Construct the metadata field for the licence by providing a URL of the form
`https://spdx.org/licenses/[SPDX-ID]` where `SPDX-ID` is the taken from the list of identifiers
`https://spdx.org/licenses/[SPDX-ID]` where `SPDX-ID` is taken from the list of identifiers
linked above. See the example snippet below for guidance. For non-standard licenses without an SPDX
identifier, provide a URL to the license.

Expand All @@ -34,8 +34,8 @@ all are required.
# other s: declarations
```

For more examples of providing metadata within CWL descriptions, see the
Metadata and Authorship section of this User Guide.
For more examples of providing metadata within CWL descriptions, see
[the Metadata and Authorship section of this User Guide](../topics/metadata-and-authorship.md).

- Include [attribution information][license-example] for the author(s) of
the CWL tool or workflow description. Use unambiguous identifiers like
Expand Down