update segmenttree docstrings Fixes #9943

[aryandgandhi]

Describe your change:

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Documentation change?

Checklist:

• [x ] I have read CONTRIBUTING.md.
• [x ] This pull request is all my own work -- I have not plagiarized.
• [x ] I know that pull requests will not be merged if they fail the automated tests.
• [x ] This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• [x ] All new Python files are placed inside an existing directory.
• [ x] All filenames are in all lowercase characters with no spaces or dashes.
• [x ] All functions and variable names follow Python naming conventions.
• [ x] All function parameters and return values are annotated with Python type hints.
• [ x] All functions have doctests that pass the automated testing.
• [x ] All new algorithms include at least one URL that points to Wikipedia or another similar explanation.
• If this pull request resolves one or more open issues then the description above includes the issue number(s) with a closing keyword: "Fixes #ISSUE-NUMBER".

[aryandgandhi]

@cclauss please approve this PR for hacktoberfest and add the hacktoberfest-accepted label after PR merging. Thank you!

[cclauss]

I gotta say that overall I am not a fan of these single variable names and uppercase variable names!!!
This looks like it was literally ported from some other language with minimal modifications.

a has no data type and no self-documenting name and the class version is uppercase. If find it unreadable.

Suggested change

	self.st = [0] * (
	4 * self.N
	) # approximate the overall size of segment tree with array N
	# approximate the overall size of the segment tree with array N
	self.st = [0] * (4 * self.N)

[aryandgandhi]

Agreed, I'll make an issue for people to tackle naming issues in the repository, seems like it was an older thing