Changed the - to * for md file

Author: BassCoder2808

DOCS/xml-fields.md

@@ -44,19 +44,16 @@ Within the .xml file, the first and last lines of the file should be the followi
 The main tag used to define the license or exception is, unsurprisingly, **`<license>`** or **`<exception>`**. All of the remaining content will be enclosed within a `<license></license>` or `<exception></exception>` pair of tags.
 
 There are two mandatory attributes for every `<license>` and `<exception>` tag:
-
-- `licenseId`: the unique SPDX Identifier for the license; should be identical to the filename
-- `name`: the longer "real name" of the license
+* `licenseId`: the unique SPDX Identifier for the license; should be identical to the filename
+* `name`: the longer "real name" of the license
 
 There are two additional attributes which are optional, but highly encouraged:
-
-- `isOsiApproved` (for licenses, not exceptions): either "true" or "false" based on whether this license has been approved by the [Open Source Initiative](https://opensource.org/licenses/alphabetical)
-- `listVersionAdded`: in which release version of the SPDX License List was the license first added, e.g. "3.19".
-  - Typically you'll check the currently-released version at https://spdx.org/licenses/ and increment the minor version by 1 for a new license.
+* `isOsiApproved` (for licenses, not exceptions): either "true" or "false" based on whether this license has been approved by the [Open Source Initiative](https://opensource.org/licenses/alphabetical)
+* `listVersionAdded`: in which release version of the SPDX License List was the license first added, e.g. "3.19".
+  * Typically you'll check the currently-released version at https://spdx.org/licenses/ and increment the minor version by 1 for a new license.
 
 Finally, if the license ID has been deprecated, one additional attribute should be included:
-
-- `deprecatedVersion`: in which release version of the SPDX License List was the license first marked as deprecated, e.g. "3.19"
+* `deprecatedVersion`: in which release version of the SPDX License List was the license first marked as deprecated, e.g. "3.19"
 
 Note that the deprecated tags refer to whether the ID has been deprecated _by SPDX_ -- in other words, if the SPDX Legal Team no longer recommends that the identifier should be used. Licenses that have been described as "deprecated" or "superseded" by the _license author_ might no longer be recommended to use for new code, but their identifiers remain valid License IDs on the SPDX License List.
 
@@ -66,15 +63,15 @@ Deprecated license identifiers will be listed at the bottom of the SPDX License
 
 There are three optional first-level metadata fields that can be nested immediately under `<license>` or `<exception>`, each of which is optional:
 
-- **`<crossRefs>`**: Defines cross-references to URLs where the license can be found in use by one or a few projects, and (if applicable) where posted by the license steward
-- **`<notes>`**: Describes general comments about the license; if deprecated, also briefly explain the reason for deprecating the license identifier
-- **`<obsoletedBys>`** (if license is deprecated): Lists the license(s) that should be used instead of this deprecated license
+* **`<crossRefs>`**: Defines cross-references to URLs where the license can be found in use by one or a few projects, and (if applicable) where posted by the license steward
+* **`<notes>`**: Describes general comments about the license; if deprecated, also briefly explain the reason for deprecating the license identifier
+* **`<obsoletedBys>`** (if license is deprecated): Lists the license(s) that should be used instead of this deprecated license
 
 ### License text
 
 Then, the actual license text would be contained within the `<text></text>` section:
 
-- **`<text>`**: Defines the actual text and templating for the license
+* **`<text>`**: Defines the actual text and templating for the license
 
 Example:
 
@@ -97,12 +94,12 @@ Example:
 
 Some portions of the license text can be surrounded by annotation tags, to denote certain sections of the license text:
 
-- **`<titleText>`**: indicates the title of the license, if specified in the license text itself
-- **`<copyrightText>`**: indicates where a copyright notice would be placed for the licensed code
-  - Note that `<copyrightText>` should _not_ be used for copyright notices that apply to the copyright in the license text itself!
-- **`<standardLicenseHeader>`**: indicates a standard way that the license recommends specifying the license, e.g. in code comments
-  - Note that `<standardLicenseHeader>` should _only_ be used if it is defined by the license text itself!
-  - Typically, this would be located in an appendix titled something like "How to apply the license to your work"
+* **`<titleText>`**: indicates the title of the license, if specified in the license text itself
+* **`<copyrightText>`**: indicates where a copyright notice would be placed for the licensed code
+  * Note that `<copyrightText>` should _not_ be used for copyright notices that apply to the copyright in the license text itself!
+* **`<standardLicenseHeader>`**: indicates a standard way that the license recommends specifying the license, e.g. in code comments
+  * Note that `<standardLicenseHeader>` should _only_ be used if it is defined by the license text itself!
+  * Typically, this would be located in an appendix titled something like "How to apply the license to your work"
 
 ### Paragraphs and newlines
 
@@ -118,11 +115,11 @@ Numbered lists (e.g., a series of numbered sections) and unnumbered lists (e.g.,
 
 Here are the basic rules:
 
-- The list as a whole should be surrounded with **`<list>...</list>`** tags.
-- Within the `<list>`, each item in the list should be surrounded with **`<item>...</item>`** tags.
-- If a list item has a section number or a bullet point at the start, the section number or bullet should be surrounded with **`<bullet>...</bullet>`** tags.
-- Sub-lists can be nested within an item, to indicate e.g. subsections within an overarching numbered section.
-- Items can also contain **`<p>...</p>`** tags, as needed if an item contains multiple paragraphs.
+* The list as a whole should be surrounded with **`<list>...</list>`** tags.
+* Within the `<list>`, each item in the list should be surrounded with **`<item>...</item>`** tags.
+* If a list item has a section number or a bullet point at the start, the section number or bullet should be surrounded with **`<bullet>...</bullet>`** tags.
+* Sub-lists can be nested within an item, to indicate e.g. subsections within an overarching numbered section.
+* Items can also contain **`<p>...</p>`** tags, as needed if an item contains multiple paragraphs.
 
 Example:
 
@@ -167,17 +164,15 @@ Note that some annotated portions of text (specifically `<titleText>` and `<copy
 Some licenses contain portions of language that can match to a variety of alternative texts. This is called "replaceable text", and is denoted with the **`<alt>...</alt>`** tag.
 
 The **<alt>** tag includes two attributes:
-
-- `name`: specifies a unique name for this matching element
-- `match`: specifies a [POSIX extended regular expression (ERE)](http://pubs.opengroup.org/onlinepubs/9699919799/) for what text will match
+* `name`: specifies a unique name for this matching element
+* `match`: specifies a [POSIX extended regular expression (ERE)](http://pubs.opengroup.org/onlinepubs/9699919799/) for what text will match
 
 Note that an example of actually-matching text should be included between the `<alt>` and `</alt>` tags, as the specified example is what will be rendered on the SPDX License List website page and in license text files provided by SPDX. To the extent a license has a "canonical" or "most commonly used" standard language, use that in the match between the `alt` tags.
 
 Learning regular expressions is outside the scope of this document. However, here are a few of the most common patterns, taken from [BSD-3-Clause](../src/BSD-3-Clause.xml) which is a good example of using several `<alt>` tags effectively:
-
-- `<alt match="are|is" name="tobe">are</alt>`: Matches if the text is either the word "are" or the word "is"
-- `<alt match="EXPRESS(ED)?" name="express">EXPRESS</alt>`: Matches if the text is either the word "EXPRESS" or the word "EXPRESSED"
-- `<alt match=".+" name="copyrightHolderAsIs">THE COPYRIGHT HOLDERS AND CONTRIBUTORS</alt>`: Matches anything as long as it consists of at least one or more characters
+* `<alt match="are|is" name="tobe">are</alt>`: Matches if the text is either the word "are" or the word "is"
+* `<alt match="EXPRESS(ED)?" name="express">EXPRESS</alt>`: Matches if the text is either the word "EXPRESS" or the word "EXPRESSED"
+* `<alt match=".+" name="copyrightHolderAsIs">THE COPYRIGHT HOLDERS AND CONTRIBUTORS</alt>`: Matches anything as long as it consists of at least one or more characters
 
 ### Other things to watch out for