Fix typo in Community Specification License#1367
Open
bact wants to merge 3 commits intospdx:developfrom
Open
Conversation
The Community Specification License has recently released a Maintenance Release to fix typos across its templates. The main one relevant to SPDX usage is at Section 2.1.1.2. where "in" was missing from a sentence. Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
bact
added
doc improvement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Community Specification License has recently released a Maintenance Release to fix typos across its templates. It does not change any License terms or requirements of the CSL; it contains only typo/errata fixes.
This PR mirrors those fixes.
The one that affects this spdx-spec repo is Section 2.1.1.2. (LICENSE, Line 27) where "in" was missing from a sentence:
Was:
Fixed to:
The typo was originally reported by @swinslow at CommunitySpecification/Community_Specification#19 and got fixed in the Maintenance Release. Te
Community Specification Maintenance Release:
Similar PR in spdx-3-model repo: spdx/spdx-3-model#1230