inconsistent fenced code block formatting or missing language identifiers

[mithilP007]

Description

Some Markdown documentation files may contain inconsistent fenced code block formatting or missing language identifiers.

This can reduce:

syntax highlighting quality
documentation readability
contributor consistency
To Reproduce
Browse Markdown files in the repository
Observe code blocks without language specifiers

Example:

const test = true;

instead of:

const test = true;

Expected Behavior

All fenced code blocks should:

include proper language identifiers
follow consistent formatting standards
improve rendered documentation readability
Suggested Fix
audit Markdown files
add missing language tags
standardize fenced block formatting
Impact

Improves:

documentation consistency
readability
syntax highlighting
contributor experience

[mithilP007]

Hi maintainers,

I would like to work on this enhancement issue.

I plan to standardize Markdown fenced code block formatting and add missing language identifiers to improve documentation readability and consistency.

Please assign this issue to me. Thank you!

[1Zakirhussain]

I would like to work on this

[kirti7617]

i would like to work on this Optimization issue

[hritikkumar07]

Hi maintainers,
I’d like to work on this issue. My approach would be:

Find all Markdown files with fenced code blocks.
Identify blocks missing language identifiers.
Add the appropriate language tag (js, cpp, bash, etc.).
Standardize the formatting of all fenced blocks.
Check the rendered Markdown to make sure highlighting and formatting look correct.
Submit the changes in a PR.

I’d be happy to take this up if it’s still available.

[JaphyFan]

你好，你的邮件已收到,我会尽快回复。祝你工作顺利，生活愉快！

[mayurimasale00]

I’d like to take this issue up.
I’ll audit the Markdown files, identify fenced code blocks missing language identifiers, add the appropriate tags, and run the relevant Markdown linting/formatting checks to verify the changes.