Visual Bug: Code Block's First Vertical Line Trimmed in Quickstart Guide

[patricnilackshan]

Description

Description:

In the Quickstart guide for the googleapis.drive module, there's a visual/UI issue with the code block under, Step 2: Create a new connector instance.

The first vertical character (e.g., C in configurable) is partially clipped when selecting the text manually using a mouse and copying with Ctrl+C. However, using the built-in copy icon copies the text correctly.

Screenshot:

See attached image showing visual clipping.

Steps to Reproduce

Steps to Reproduce:

1. Visit the Quickstart guide
2. Go to Step 2: Create a new connector instance
3. Try selecting the entire code block manually and copy using Ctrl+C
4. Paste the result into any text editor — the first characters on some lines may be missing or cut off.
5. Now use the copy icon in the top-right of the code block and paste — this works correctly.

Expected Behavior:

Text copied manually via mouse and Ctrl+C should include all characters exactly as displayed.

Actual Behavior:

When selecting manually, the first character of each line appears clipped visually and sometimes missing in the copied result.

Version

https://central.ballerina.io/ballerinax/googleapis.drive/latest

Environment Details (with versions)

https://central.ballerina.io/ballerinax/googleapis.drive/latest

[sm1990]

@ThisaruGuruge remove the extra line after ballerina (https://github.com/ballerina-platform/module-ballerinax-googleapis.drive/blob/1a362cf5c51fc77ec06289cb33085b92b1e25a20/ballerina/Module.md?plain=1#L25). Trailing whitespaces causes incorrect rendering.

[ThisaruGuruge]

Can't we fix this trailing white space issue from the renderer?

IIRC, there were similar issues reported when there is a space after the ballerina identifier too.
In this case, we have to release a new version of the package just by removing a single empty line, which IMO, redundant.

Additionally, from the documentation point of view, this is not incorrect. (Although I agree it isn't align well with the conventions). But when rendering/generating docs, I don't think we should expect everything/everyone to follow the conventions (especially if a 3rd party developer pushes a package to Ballerina Central). Therefore, IMO, I think we should fix this from the rendering side.

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.