From a4e640d900ed4c601c4f0da13f020e5408484564 Mon Sep 17 00:00:00 2001
From: Philip Withnall <pwithnall@endlessos.org>
Date: Fri, 5 Mar 2021 20:07:54 +0000
Subject: [PATCH] spec: Fix case of LicenseRef-proprietary in the spec

As per discussion on #309, it should be `LicenseRef-proprietary`, rather
than `LicenseRef-Proprietary`.

Signed-off-by: Philip Withnall <pwithnall@endlessos.org>

Helps: #309
---
 docs/xml/metainfo-component.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/xml/metainfo-component.xml b/docs/xml/metainfo-component.xml
index b1f8356b0..fc40b4fb4 100644
--- a/docs/xml/metainfo-component.xml
+++ b/docs/xml/metainfo-component.xml
@@ -1037,14 +1037,14 @@
 					<listitem><para><literal>LGPL-3.0+ AND GPL-3.0+</literal></para></listitem>
 					<listitem><para><literal>MIT</literal></para></listitem>
 					<listitem><para><literal>CC-BY-SA-2.0</literal></para></listitem>
-					<listitem><para><literal>LicenseRef-Proprietary=https://example.com/mylicense.html</literal></para></listitem>
+					<listitem><para><literal>LicenseRef-proprietary=https://example.com/mylicense.html</literal></para></listitem>
 				</itemizedlist>
 				A full list of recognized licenses and their identifiers can be found at the
 				<ulink url="https://spdx.org/licenses/">SPDX OpenSource License Registry</ulink>.
 			</para>
 			<para>
 				Custom licenses which are not in the SPDX registry, like proprietary licenses, can be denoted using the <code>LicenseRef</code> notation.
-				<code>LicenseRef-Proprietary</code> can be used to denote a proprietary license, with an optional URL to the license text following after
+				<code>LicenseRef-proprietary</code> can be used to denote a proprietary license, with an optional URL to the license text following after
 				a <code>=</code> sign.
 			</para>
 			<para>