build: address PR feedback

---
type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes.
report:
  - task: lint_filenames
    status: passed
  - task: lint_editorconfig
    status: passed
  - task: lint_markdown
    status: na
  - task: lint_package_json
    status: na
  - task: lint_repl_help
    status: na
  - task: lint_javascript_src
    status: na
  - task: lint_javascript_cli
    status: na
  - task: lint_javascript_examples
    status: na
  - task: lint_javascript_tests
    status: na
  - task: lint_javascript_benchmarks
    status: na
  - task: lint_python
    status: na
  - task: lint_r
    status: na
  - task: lint_c_src
    status: na
  - task: lint_c_examples
    status: na
  - task: lint_c_benchmarks
    status: na
  - task: lint_c_tests_fixtures
    status: na
  - task: lint_shell
    status: passed
  - task: lint_typescript_declarations
    status: na
  - task: lint_typescript_tests
    status: na
  - task: lint_license_headers
    status: passed
---

Author: Planeshifter

.github/workflows/scripts/check_tracking_issue_closure

@@ -59,7 +59,7 @@ repo_owner="stdlib-js"
 repo_name="stdlib"
 
 # Regular expressions for auto-closing language:
-closing_keywords="(resolves|closes|fixes|resolved|closed|fixed)"
+closing_keywords="(close|closes|closed|fix|fixes|fixed|resolve|resolves|resolved)"
 
 # Unique identifier for our bot comments:
 comment_identifier="<!-- stdlib-bot-tracking-issue-closure-check -->"
@@ -188,12 +188,14 @@ post_comment() {
 I noticed your PR description contains closing keywords (\"Resolves\", \"Closes\", or \"Fixes\") referencing a \"Tracking Issue\".
 
 **Why this matters:**
-Tracking issues should typically remain open until all related sub-issues are completed. GitHub automatically closes issues with such closing keywords when the PR is merged.
+Tracking issues should typically remain open until all related sub-issues are completed. GitHub automatically closes issues with such closing keywords when the PR is merged. For more information, see [GitHub's documentation on using keywords in issues and pull requests][github-keywords].
 
 **Required action:**
 Use \"Progresses\" instead to reference the tracking issue without automatically closing it.
 
-Thank you for your contribution to the project!"
+Thank you for your contribution to the project!
+
+[github-keywords]: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests"
 
 	# Create properly escaped JSON payload using jq
 	json_payload=$(jq -n --arg body "$comment_body" '{"body": $body}')