Editorial updates on column IDs and Display Names

[jpradocueva]

These changes won't affect the content in Release V1.1. They are actually editorial guidelines according to the working group agreement.

[jpradocueva]

This issue was originated during the discussion of #469

[jpradocueva]

Action Items from TF-2 call on October 3rd:

• [TF2-#582] Members: Coordinate with the editorial team to finalize minor changes by Monday.

[jpradocueva]

Action Items assigned during TF-2 call on Oct 15:

• [TF-1-#582] Joaquin, @jpradocueva: Fix double colon issues in Column IDs and obtain final approval.

[ijurica]

In this PR, I’m unable to add a comment/suggestion directly in the appropriate place in the table, so I’m suggesting here that we add the following row.

<tr>
    <td><strong>Column Values:</strong></td>
    <td>		   
        - "Usage"<br> 
        - "Tax"<br> 
        - "TB"<br>
    </td>
    <td>
        This column:
        * MUST be null when ChargeCategory is "Tax"... 
    </td>
    <td>
        - Enclosed in double quotation marks<br>
        - Normal text without bold or italics
    </td>
</tr>

Note:
Note: We have consistently formatted normalized column values as normal text without bold or italics, enclosed in double quotation marks. On the other hand, for non-normalized column values, we've been using various formatting, such as:

• "TB"
• Hours
• Compute Usage

I suggest we keep it simple and use normal text without bold or italics, enclosed in double quotation marks for all column values, both normalized and non-normalized. However, I don't have a strong preference.

If we plan to distinguish the formatting for normalized and non-normalized columns, do we need to clarify what those terms mean? We internally use "normalized" and "non-normalized" columns but haven't specified their definitions.

[jpradocueva]

@ijurica, I suggest that you add this extra row to the table so it is easy to review. If the group disagrees with the change, it can be removed.

[ijurica]

Nit: add <br> in line 60

[jpradocueva]

Approved during the Members' call on Oct 17.