Skip to content

Commit 62f3e7c

Browse files
briandealwisgoneall
authored andcommitted
Fix how-to-use bullet rendering
Add blank line and use `*` bullet style as used elsewhere (such as chapters/conformance.md) Signed-off-by: Brian de Alwis <[email protected]>
1 parent ecacc87 commit 62f3e7c

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

chapters/how-to-use.md

+5-4
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,11 @@
55
SPDX 2.x has the concept of an External Reference for a Package to "reference an external source of additional information, metadata, enumerations, asset identifiers, or downloadable content believed to be relevant to the Package."
66

77
The specification for External Reference identifiers (Annex F) has four defined categories:
8-
- Security: CPE, SWID tag identifier, or reference to security information
9-
- Package-Manager: package identifier and locator
10-
- Persistent-id: identifier which is guaranteed to remain stable (persistent) over time
11-
- Other: Use if none of the above match your use case
8+
9+
* Security: CPE, SWID tag identifier, or reference to security information
10+
* Package-Manager: package identifier and locator
11+
* Persistent-id: identifier which is guaranteed to remain stable (persistent) over time
12+
* Other: Use if none of the above match your use case
1213

1314
This section provides usage scenarios of how to leverage the Security and Persistent-id category external references specified above to refer to external security information. A complete SPDX document using these can be found in the examples directory within the SPDX code repository. Multiple instances and types of external security information may be included within a SPDX document.
1415

0 commit comments

Comments
 (0)