API description review findings

[MarkusKuemmerle]

Problem description
CAMARA Outreach team is reviewing all API descriptions on the CAMARA website using a checklist.

Possible evolution
In case of findings an issue is opened to ask the Sub Project to enhance the API description in the Wiki, and then open an issue at the Marketing repo so that the Outreach team then can update the website.

Alternative solution

Additional context

Findings in Carrier Billing:

• Please check the first section below the visual. Should we change "mobile line" to "mobile phone number"?
• Is it correct that the API requires always 3-legged authentication?
• What are OB Carrier Billing Systems? Can you replace the abbreviation "OB" by the long term?
• Use Case section: Please check if you can link exisiting use cases in the GSMA use case library
• Use Case section: The use case name should be in bold, the explanation in normal font. Possibly you can use "Direct Carrier Billing" as name in bold.
• Benefits section: The benefit name should be in bold, followed by a colon. And then the description in normal font.
• The image should visualize the most interesting use case to attract customers and developers. Please provide us instructions how such a visual should be built and look like. We ask the LF creative team to create the visual. You can put the instructions also in the wiki page below the visual.