[EDITORIAL] Column doc link formatting fix

[AWS-ZachErdman]

We inconsistently wrote the names of columns in the links that link to columns throughout the spec. Sometimes they would have a space between words and sometimes not. I adjusted all column links to have no spacing between words to make it clear it was a column.

I also fixed a link to ContractedUnitPrice that incorrectly linked to the glossary.

[jpradocueva]

Should Numeric Format be updated?

[AWS-ZachErdman]

Should Numeric Format be updated?

I don't think that's needed since it's not a column in FOCUS, so it wouldn't appear as NumericFormat.

[jpradocueva]

@AWS-ZachErdman The group discussed this topic and indicated that it was intentionally defined with a blank space when the column is not listed as a Mandatory requirement.

[AWS-ZachErdman]

I see - when the column is being referenced in a requirement, it's supposed to not have a space.

[jpradocueva]

Extracted from the Members' Group, Meeting Minutes, May 23.

Some members noted that certain names were intentionally defined with a space, such as "Billing Currency" instead of "BillingCurrency." This distinction helps differentiate when the column name is used in a general context versus the column Name ID, which is employed in normative statements.

The group agreed to create editorial guidelines to address this type of issues.

[jpradocueva]

Action Items from TF-1 call on October 1st:

• TF1-#469 Joaquin, @jpradocueva : Prepare editorial guidelines reflecting agreed column naming conventions.

[jpradocueva]

PR #582 contains editorial guidelines to resolve this issue.