While you are there, please change b to strong.

@infograf768 with the extra markup, I am now wondering if the only points that need to be emphasised are as below... the first sentence is already given pre filled with the option to change. Whereas the second sentence is an instruction if the default isn't used.

Choose a table prefix or use the randomly generated one, ideally four or five characters long. It may only contain alphanumeric characters and MUST end in an underscore. Make sure that the prefix chosen is not used by other tables.

Choose a table prefix or use the randomly generated one, ideally four or five characters long. It may only contain alphanumeric characters and MUST end in an underscore. Make sure that the prefix chosen is not used by other tables.

IMHO the strong should only be used if is really really important to call for the end user attention.
Also i think you either uses CAPITALIZATION or you use strong, using CAPITALIZATION WITH STRONG, in my personal view, is an overkill and not user friendly.

I think bold in the "must" is enough to call the user attention and still be easily read.

BTW why the "may" and the "MUST" ... aren't both "MUST"?

My proposal:

Create a table prefix or use the randomly generated one. Ideally four or five characters long, it must contain only alphanumeric characters and end in an underscore. Also, make sure that the prefix chosen is not already used by other tables.

Out of the 3 sentences the 2nd and 3rd are the ones that carry an instruction, I am happy to put the PR forward in all lower case and no emphasis, as I suspect the only time it is read is when someone is installing for the first time, and then they are more likely to read each word and stay with the randomly generated one.

@andrepereiradasilva
The reason for a may and a must come from my work and using legally binding documentation where instructions are formatted in a particular way.
With the "Must" it is an instruction which has something which has to be followed ie it must end in an underscore.
However "May only" gives a degree of optionality, as in we are not instructing that it must contain both letters and numbers, rather it "may only" contain letters or numbers. it's just semantics for a project like Joomla mind.

Am open to any option mind, as minor as it is the wording could be improved.

May and must seem correct to me ( as the only non-lawyer in my family :) l

Out of the 3 sentences the 2nd and 3rd are the ones that carry an instruction, I am happy to put the PR forward in all lower case and no emphasis, as I suspect the only time it is read is when someone is installing for the first time, and then they are more likely to read each word and stay with the randomly generated one.

ok.

The reason for a may and a must come from my work and using legally binding documentation where instructions are formatted in a particular way.
With the "Must" it is an instruction which has something which has to be followed ie it must end in an underscore.
However "May only" gives a degree of optionality, as in we are not instructing that it must contain both letters and numbers, rather it "may only" contain letters or numbers. it's just semantics for a project like Joomla mind.

May and must seem correct to me ( as the only non-lawyer in my family :) l

2 to 1, let's democracy play. You win :)

I have tested this item successfully on 07446df

I have tested this item successfully on 07446df

RTC