To test whether string s is a reserved identifier you have to call keyword.iskeyword(s), not keyword.iskeyword().

I don't think anything should be changed here. Currently the link removes even the smallest chance of misunderstanding it. IMHO changes will make the documentation worse.

In my suggestion on the issue, I specifically included the argument '(s)' in the call so that 's' later in the sentence referred back to the string passed as an argument. I changes the vague 'use' to the specific 'call'. 'test for reserved identifiers' is awkward. Test what? (especially with the subject s never mentioned). Changes are not always bad.

I like the following, based on Serhiy's comment, even better as a followup to the preceding sentence.

To test whether string s is a reserved keyword, such as def or class, call keyword.iskeyword(s).

Sure, I will change to that. The only issue I faced adding an argument in the function is that it is not hyperlinked in the html docs if I did :func:keyword.iskeyword(s). Although :func:keyword.iskeyword works fine.

I searched the docs for a similar function reference that accepts an argument but I couldn't find. Can you please guide me on how do I change it so that it is also hyperlinked to the actual method definition in the html docs?

This is the reason why I suggest to not change the current documentation. It is good enough and changes make it worse: technically incorrect, more verbose, or less informative.

CuriousLearner: I presume, but don't know for sure, that you can pur '(x)' outside the backticks and get the hyperlink.

Serhiy: Either proposed change, the second of which is based on your statement, is more informative, not less, and more technically correct, not less. Your said it yourself. iskeyword "test[s] whether string s is a reserved identifier [singular]", whereas the somewhat cryptic 'test for reserved identifiers [plural]' can easily be expanded to and construed as meaning 'test whether string s contains reserved identifiers [plural]". The IDLE colorizer does just that. It 'tests for reserved keywords', in this sense, and when it finds them, tags them.

@terryjreedy I already tried that & it does not get hyperlinked correctly.

@Mariatta Can you help here please?

Adding an example would clarify the usage and differences:

Keywords, which are a small subset of identifiers used as reserved words, are not ordinary identifiers. To test if a string is a keyword, call :func:keyword.iskeyword to test whether a string s is a reserved identifier, such as :keyword: def and :keyword:class.

An example shows their usage:

>>> import keyword

>>> string_ordinary = 'hello'
>>> string_keyword = 'def'

>>> string_ordinary.isidentifier()
True
>>> keyword.iskeyword(string_ordinary)
False
>>> string_keyword.isidentifier()
True
>>> keyword.iskeyword(string_keyword)
True

This proposed change is in an entry about identifiers, not keywords. Expanding the keyword module doc would be a separate discussion. If we did something, I would it a bit shorter, such as

>>> from keyword import iskeyword

>>> 'hello'.isidentifier(), iskeyword('hello')
True, False
>>> 'def'.isidentifier(), iskeyword('def')
True, True

I like @terryjreedy’s suggested example. More compact but captures the importance of contrasting both uses.