Skip to content

[General Docs] Audit/Cleanup of Track General/Shared Docs #4237

Description

@Yrahcaz7

This is a tracking issue for errors in the general docs on the Python track.

The docs are split into the below categories (general, shared, and other) depending on their location in the repo.

General Docs (docs/)

  • ABOUT.md (addressed in PR 4254):

    details
  • GENERATOR.md:

    details
    • Lines 7 to 18: Was this table of contents automatically generated by a tool? If it was manually created (or if it is possible to configure the tool otherwise), the top-level header "Exercism Python Track Test Generator" should probably be excluded.
    • Line 40: The word-count additional tests path has changed, it is now exercises/practice/word-count/.meta/additional_tests.json
    • Line 45: The example is missing a % at the end of the if statement. It should be: {% for case in cases %}{% if case is error_case %}
    • Line 54: The footer macro no longer exists. This should be probably be changed to mention macros.canonical_ref() and/or macros.header() instead.
    • Line 60: "option file" should be "optional file"
    • Lines 60-61: The wording here is a bit awkward, maybe "is to have" could be changed to "should have"?
    • Lines 60-62: The second sentence should be on its own line.
    • Lines 71-90: This part seems outdated; it uses the footer macro that no longer exists. It should probably be updated based on master_template.j2.
    • Line 95: There should be a space after the "ex:"
    • Line 98 would be more readable if there was a space between the ) and the }}, like so: "{{ macros.header(["Clock"]) }}".
    • Line 122: "templates" should be "template" here.
    • Line 131: This inline link should be converted into a reflink.
  • INSTALLATION.md:

    details
    • Line 15: There should be punctuation in between "Windows" and "Additionally".
    • Line 16 is missing a period at the end.
    • Line 19: Is this line supposed to be indented? It doesn't seem to be a continuation of the last list item.
    • Line 22: Python 3.13.5 should be Python 3.13.13.
    • Lines 24-25 are a bit awkward, maybe they could be merged into one sentence: "Most of the exercises will work with Python 3.6+ or even earlier versions, but we don't guarantee support for versions not listed under Active Python Releases."
    • Lines 32-33 and 34-35: These pairs of reflinks are the same. Is this intentional?
    • Line 38: This link now redirects to "https://learn.microsoft.com/en-us/windows/dev-environment/python".
  • LEARNING.md:

    details
  • PROBLEM-SOLVING.md (addressed in PR 4253):

    details
  • RESOURCES.md:

  • TDD.md:

    details
    • Line 7: It isn't completely clear what "implementation-specific design" means.
    • The paragraph on lines 5-12 is rather long and would benefit from being split up, perhaps into smaller paragraphs or a list.
    • Lines 18-19 are rather confusing. Perhaps they could be changed to something like: "Although it is sometimes called 'refactoring' to modify code to get it to pass the tests, this is only actually 'refactoring' if it improves the design of the code. Simply debugging without improving the design is not refactoring."
    • Troubleshooting a Failed Test on Exercism in the Web Editor section:
      • Line 78 (and others): "Test 1 is usually going to be a kind of template with a code section for setting up the tests" seems to no longer be true. Any template/setup seems to no longer be shown to the student.
      • Line 92-93: The tests no longer have the inputs and outputs in the headers. This should just be "FAILED TisburyTreasure > get coordinate [variation #1]".
      • Line 99: Is "likely" necessary? I can't think of a case where the information is not shown in a code section.
      • Line 100: Are there actually any cases where the tests share the data?
      • Line 110: It isn't entirely clear that this is a continuation of the example. Perhaps it could be changed to: "In this example, the problematic code is as follows:" or "The code for get_coordinate() here might look like the following:"
      • Since the whole section is about concept exercises, and most of the ideas apply to all exercises, it should include a sentence like: "This section only covers concept exercises, but the process is very similar for practice exercises."
    • Line 140 is a bit awkward, maybe it could be: "If a mentor is available, they may contact you with ideas for improvements or other approaches."
    • Line 145: A link to a source with more context would be helpful here.
    • Line 154 is confusing. Maybe it could be changed to: "The more times the stmt code is run, the less the setup time will count towards the result."
    • The paragraph on lines 145-159 is very long and would benefit from being split up.
    • Line 175 is an unnecessary blank line. Having a blank line after line 179 instead would probably improve readability. (This also applies to the next code block on lines 187-202.)
    • In the last two codeblocks, the usage of quotes is inconsistent. VOWELS = "AEIOU" should probably be changed to VOWELS = 'AEIOU'.
    • The links to "www.agilealliance.org" and "www.machinelearningplus.com" now redirect to "agilealliance.org" and "machinelearningplus.com" respectively.

Shared Docs (exercises/shared/.docs/)

TBA

Other (CONTRIBUTING.md, README.md)

TBA

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions