doc: add an example code

[PoojaDurgad]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[Trott]

Suggested change

	console.log(`Current groups: ${process.getgroups()}`);
	console.log(process.getgroups()); // [ 16, 21, 297 ]

Embedding it in a string might make it less clear what the output is in this case. Raw array output might be better.

[PoojaDurgad]

@Trott - I understand your point and thanks for the review. I have followed your suggestion. Please have a look.

[Trott]

Landed in f59d4e0

@PoojaDurgad I usually don't bother contributors with this detail, but because you are opening a lot of pull requests: Usually, only the first commit needs to be formatted according to our guidelines. For subsequent commits that are small changes to your pull requests (such as in this one where you had a second commit that removed extraneous whitespace and a third commit that implemented a small suggestion from a reviewer), it helps if you use git commit --fixup HEAD rather than writing a commit message. This will both let someone who lands the commit manually use --autosquash and it also means that your pull requests can be correctly landed by the bot we use (because it will run --autosquash if it can).

[PoojaDurgad]

@Trott - Thanks for the suggestion. I will follow up.