Search code, repositories, users, issues, pull requests...

docs/using_older_sdks_with_open_pru.md[199]

+[PRU Academy for AM243x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM24X-ACADEMY__ZPSnq-h__LATEST)  
+[PRU Academy for AM64x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM64-ACADEMY__WI1KRXP__LATEST)

Evidence
Compliance rule 16 requires lines to generally stay within 79 columns and never exceed 129 columns;
the newly added academy link lines contain very long URLs on a single line, exceeding the hard
limit.
docs/release_notes.md[69-70]
docs/release_notes.md[131-132]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains newly added markdown link lines with long URLs that exceed the 129-column hard limit.
## Issue Context
Compliance requires lines to generally stay within 79 columns and never exceed 129 columns.
## Fix Focus Areas
- docs/release_notes.md[69-70]
- docs/release_notes.md[131-132]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

5. Commit URL line too long 📘 Rule violation ✓ Correctness

Description

The added inline commit link is a long single line that exceeds the repository’s line-length/layout
standard for docs. Use a reference-style link (or wrap) to keep the line within limits.

Code

+[AM243x & AM64x: Add support for MCU+ SDK 11.1&11.2](https://github.com/TexasInstruments/open-pru/commit/a29c10dbb4348065d13ba91af515e64e517e11a5)

Evidence
PR Compliance ID 12 and 23 require repository-standard text layout and maintainable Markdown
formatting, including avoiding overly long unreflowed lines. The added commit link is a single long
inline URL line.
docs/using_older_sdks_with_open_pru.md[199-199]
Best Practice: Repository guidelines
Best Practice: Learned patterns

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A newly added inline commit URL in `docs/using_older_sdks_with_open_pru.md` is an overly long single line and violates repository line-length/layout guidance.
## Issue Context
Docs should keep lines within the documented limits; reference-style links are typically used to avoid long inline URLs.
## Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[199-199]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

6. Unwrapped academy URLs exceed limit 📘 Rule violation ✓ Correctness

Description

docs/release_notes.md includes long unwrapped markdown link lines that likely exceed the
129-column hard limit. This violates the repository formatting rules and can reduce diff readability
and portability across tools.

Code

docs/release_notes.md[5-13]
docs/release_notes.md[40-43]

+[PRU Academy for AM243x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM24X-ACADEMY__ZPSnq-h__LATEST)  
+[PRU Academy for AM64x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM64-ACADEMY__WI1KRXP__LATEST)

Evidence
Compliance rule 16 requires lines to generally stay within 79 columns and never exceed 129 columns;
the newly added academy link lines contain very long URLs on a single line, exceeding the hard
limit.
docs/release_notes.md[69-70]
docs/release_notes.md[131-132]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains newly added markdown link lines with long URLs that exceed the 129-column hard limit.
## Issue Context
Compliance requires lines to generally stay within 79 columns and never exceed 129 columns.
## Fix Focus Areas
- docs/release_notes.md[69-70]
- docs/release_notes.md[131-132]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

7. Duplicate Release Notes header 🐞 Bug ✓ Correctness

Description

The file now has both an H1 and an H2 named "Release Notes", so the TOC link #release-notes will
land on the top H1 instead of the versioned section header (GitHub disambiguates duplicates by
appending -1). This degrades navigation and makes the TOC misleading.

Code

docs/release_notes.md[R40-43]
+## Release Notes
+
+### v2026.00.00
+

Evidence

The TOC links #release-notes, but there are two headings with the same text; the later one is the
actual start of the versioned notes, so the link target will not match reader intent.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains both `# Release Notes` and `## Release Notes`. The TOC entry `[Release Notes](#release-notes)` will navigate to the first heading (the H1), not the section where versioned release notes begin.
### Issue Context
GitHub generates the same slug for same-text headings and disambiguates subsequent duplicates (e.g., `release-notes-1`). This makes the current TOC link misleading.
### Fix Focus Areas
- docs/release_notes.md[9-13]
- docs/release_notes.md[40-43]
### Suggested direction
- Option A (preferred): Rename the H2 to something unique like `## Release Notes by Version` and update the TOC link accordingly.
- Option B: Remove the `## Release Notes` H2 entirely and let the TOC jump directly to `v2026.00.00` / `v2025.00.00`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

8. PR linked as commit 🐞 Bug ✓ Correctness

Description

The new older-SDK guidance says "OpenPRU commit" but links to a GitHub pull request URL. This can
confuse readers looking for an exact commit to revert (or whether they should revert a series of
changes).

Code

+In order to undo these changes, revert the file changes that were done in
+OpenPRU commit
+[AM243x & AM64x: Add support for MCU+ SDK 11.1&11.2](https://github.com/TexasInstruments/open-pru/pull/110)

Evidence

The wording explicitly says "commit" while the URL clearly points to /pull/110 (a PR), creating a
terminology/link mismatch.

docs/using_older_sdks_with_open_pru.md[97]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The doc says &amp;quot;OpenPRU commit&amp;quot; but links to a pull request (`/pull/110`). This mismatch can confuse users following revert instructions.
### Issue Context
A PR link may be intentional/preferable (it provides full context and may include multiple commits). If so, the text should call it a PR/changes introduced in the PR.
### Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[197-199]
### Suggested direction
- Change wording to e.g. &amp;quot;revert the file changes introduced in OpenPRU PR #110&amp;quot;.
- If you want a single commit reference, replace the link with the specific commit URL and keep &amp;quot;commit&amp;quot;.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

9. Ambiguous section-7 anchor 🐞 Bug ✓ Correctness

Description

The new link to section 7 uses an anchor containing "11-1" while the target header contains "11.1".
Because the file does not define an explicit HTML anchor, navigation relies on the markdown
renderer’s auto-generated ID rules; punctuation handling may cause the link to not jump to the
intended section on GitHub (or other renderers).

Code

+[7. Revert MCU+ SDK 11.1 makefile updates](#7-revert-mcu-sdk-11-1-makefile-updates). Affects: AM243x & AM64x MCU+ cores

Evidence

The link is authored with an explicit fragment "#7-revert-mcu-sdk-11-1-makefile-updates" but the
only target section is the H2 header text containing "11.1" (with a dot). Since there is no explicit
anchor ID defined in the markdown, correct navigation depends on how the renderer converts "11.1"
into an ID. The repo already demonstrates elsewhere that dotted version headers are linked by
removing dots (e.g., "v2026.00.00" -> "#v20260000"), which suggests the same dot-removal behavior
may apply here and make "11-1" not match.

docs/using_older_sdks_with_open_pru.md[95-99]
docs/using_older_sdks_with_open_pru.md[189-194]
docs/release_notes.md[9-13]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The internal link to section 7 uses a fragment identifier containing `11-1`, but the destination header contains `11.1`. Because there is no explicit HTML anchor, the link depends on markdown renderer auto-ID rules and may not navigate correctly.
### Issue Context
- Link: `[7. ...](#7-revert-mcu-sdk-11-1-makefile-updates)`
- Destination header: `## 7. Revert MCU+ SDK 11.1 makefile updates`
### Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[95-99]
- docs/using_older_sdks_with_open_pru.md[189-190]
### Suggested fix options
1) **Stable explicit anchor** (most robust across renderers):
 - Add an explicit anchor before the header, e.g.:
   - `&amp;lt;a id=&amp;quot;7-revert-mcu-sdk-11-1-makefile-updates&amp;quot;&amp;gt;&amp;lt;/a&amp;gt;`
 - Keep the existing link fragment as-is.
2) **Match GitHub-style auto ID**:
 - Change the link fragment to the actual auto-generated header ID (likely dot-removed), e.g. `#7-revert-mcu-sdk-111-makefile-updates` if using GitHub-style dot stripping.
 - Prefer option (1) if you want to avoid relying on auto-ID conventions.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

View more (2)

10. Duplicate Release Notes header 🐞 Bug ✓ Correctness

Description

The file now has both an H1 and an H2 named "Release Notes", so the TOC link #release-notes will
land on the top H1 instead of the versioned section header (GitHub disambiguates duplicates by
appending -1). This degrades navigation and makes the TOC misleading.

Code

docs/release_notes.md[R40-43]
+## Release Notes
+
+### v2026.00.00
+

Evidence

The TOC links #release-notes, but there are two headings with the same text; the later one is the
actual start of the versioned notes, so the link target will not match reader intent.

docs/release_notes.md[5-13]
docs/release_notes.md[40-43]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains both `# Release Notes` and `## Release Notes`. The TOC entry `[Release Notes](#release-notes)` will navigate to the first heading (the H1), not the section where versioned release notes begin.
### Issue Context
GitHub generates the same slug for same-text headings and disambiguates subsequent duplicates (e.g., `release-notes-1`). This makes the current TOC link misleading.
### Fix Focus Areas
- docs/release_notes.md[9-13]
- docs/release_notes.md[40-43]
### Suggested direction
- Option A (preferred): Rename the H2 to something unique like `## Release Notes by Version` and update the TOC link accordingly.
- Option B: Remove the `## Release Notes` H2 entirely and let the TOC jump directly to `v2026.00.00` / `v2025.00.00`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

11. PR linked as commit 🐞 Bug ✓ Correctness

Description

The new older-SDK guidance says "OpenPRU commit" but links to a GitHub pull request URL. This can
confuse readers looking for an exact commit to revert (or whether they should revert a series of
changes).

Code

+In order to undo these changes, revert the file changes that were done in
+OpenPRU commit
+[AM243x & AM64x: Add support for MCU+ SDK 11.1&11.2](https://github.com/TexasInstruments/open-pru/pull/110)

Evidence

The wording explicitly says "commit" while the URL clearly points to /pull/110 (a PR), creating a
terminology/link mismatch.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The doc says &amp;amp;quot;OpenPRU commit&amp;amp;quot; but links to a pull request (`/pull/110`). This mismatch can confuse users following revert instructions.
### Issue Context
A PR link may be intentional/preferable (it provides full context and may include multiple commits). If so, the text should call it a PR/changes introduced in the PR.
### Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[197-199]
### Suggested direction
- Change wording to e.g. &amp;amp;quot;revert the file changes introduced in OpenPRU PR #110&amp;amp;quot;.
- If you want a single commit reference, replace the link with the specific commit URL and keep &amp;amp;quot;commit&amp;amp;quot;.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

12. FIR typo in notes 🐞 Bug ✓ Correctness

Description

The FIR example description misspells "Response" as "Respose". This reduces doc quality and makes
searching for the term harder.

Code

+* Add examples/fir
+  * Implement 64-tap Finite Impulse Respose (FIR) filter on PRU
+  * supports AM243x

Evidence

The added bullet contains a spelling error in a technical term (FIR stands for Finite Impulse
Response).

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The release notes text for the FIR example has a typo: &amp;quot;Respose&amp;quot; instead of &amp;quot;Response&amp;quot;.
### Issue Context
FIR is a standard acronym for *Finite Impulse Response*; the typo also reduces searchability.
### Fix Focus Areas
- docs/release_notes.md[85-87]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

13. FIR typo in notes 🐞 Bug ✓ Correctness

Description

The FIR example description misspells "Response" as "Respose". This reduces doc quality and makes
searching for the term harder.

Code

+* Add examples/fir
+  * Implement 64-tap Finite Impulse Respose (FIR) filter on PRU
+  * supports AM243x

Evidence

The added bullet contains a spelling error in a technical term (FIR stands for Finite Impulse
Response).

docs/using_older_sdks_with_open_pru.md[187]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The release notes text for the FIR example has a typo: &amp;amp;quot;Respose&amp;amp;quot; instead of &amp;amp;quot;Response&amp;amp;quot;.
### Issue Context
FIR is a standard acronym for *Finite Impulse Response*; the typo also reduces searchability.
### Fix Focus Areas
- docs/release_notes.md[85-87]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

ⓘ The new review experience is currently in Beta. Learn more

Previous review results

Review updated until commit 048e6a9

Results up to commit e953750

🐞 Bugs (4) 📘 Rule violations (3) 📎 Requirement gaps (0)

1. FAQ URL line too long 📘 Rule violation ✓ Correctness ⭐ New

Description

The added inline FAQ link is an excessively long single line, violating the repository’s
line-length/layout standard for docs. Use a reference-style link (or wrap) to keep the line within
limits.

Code

+[[FAQ] AM62x & AM64x: How to enable PRU RPMsg on Processor SDK Linux 11.0](https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1494495/faq-am62x-am64x-how-to-enable-pru-rpmsg-on-processor-sdk-linux-11-0).

Evidence
PR Compliance ID 12 and 23 require repository-standard text layout and maintainable Markdown
formatting, including avoiding overly long unreflowed lines. The added FAQ link is a single long
inline URL line.
docs/using_older_sdks_with_open_pru.md[187-187]
Best Practice: Repository guidelines
Best Practice: Learned patterns

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A newly added inline URL in `docs/using_older_sdks_with_open_pru.md` is an overly long single line and violates repository line-length/layout guidance.

## Issue Context
Docs should keep lines within the documented limits; reference-style links are typically used to avoid long inline URLs.

## Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[187-187]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Commit URL line too long 📘 Rule violation ✓ Correctness ⭐ New

Description

The added inline commit link is a long single line that exceeds the repository’s line-length/layout
standard for docs. Use a reference-style link (or wrap) to keep the line within limits.

Code

docs/using_older_sdks_with_open_pru.md[199]

+[AM243x & AM64x: Add support for MCU+ SDK 11.1&11.2](https://github.com/TexasInstruments/open-pru/commit/a29c10dbb4348065d13ba91af515e64e517e11a5)

Evidence
PR Compliance ID 12 and 23 require repository-standard text layout and maintainable Markdown
formatting, including avoiding overly long unreflowed lines. The added commit link is a single long
inline URL line.
docs/using_older_sdks_with_open_pru.md[199-199]
Best Practice: Repository guidelines
Best Practice: Learned patterns

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A newly added inline commit URL in `docs/using_older_sdks_with_open_pru.md` is an overly long single line and violates repository line-length/layout guidance.

## Issue Context
Docs should keep lines within the documented limits; reference-style links are typically used to avoid long inline URLs.

## Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[199-199]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. Unwrapped academy URLs exceed limit 📘 Rule violation ✓ Correctness

Description

docs/release_notes.md includes long unwrapped markdown link lines that likely exceed the
129-column hard limit. This violates the repository formatting rules and can reduce diff readability
and portability across tools.

Code

docs/using_older_sdks_with_open_pru.md[97]

+[PRU Academy for AM243x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM24X-ACADEMY__ZPSnq-h__LATEST)  
+[PRU Academy for AM64x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM64-ACADEMY__WI1KRXP__LATEST)

Evidence
Compliance rule 16 requires lines to generally stay within 79 columns and never exceed 129 columns;
the newly added academy link lines contain very long URLs on a single line, exceeding the hard
limit.
docs/release_notes.md[69-70]
docs/release_notes.md[131-132]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains newly added markdown link lines with long URLs that exceed the 129-column hard limit.
## Issue Context
Compliance requires lines to generally stay within 79 columns and never exceed 129 columns.
## Fix Focus Areas
- docs/release_notes.md[69-70]
- docs/release_notes.md[131-132]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

4. Ambiguous section-7 anchor 🐞 Bug ✓ Correctness ⭐ New

Description

The new link to section 7 uses an anchor containing "11-1" while the target header contains "11.1".
Because the file does not define an explicit HTML anchor, navigation relies on the markdown
renderer’s auto-generated ID rules; punctuation handling may cause the link to not jump to the
intended section on GitHub (or other renderers).

Code

+[7. Revert MCU+ SDK 11.1 makefile updates](#7-revert-mcu-sdk-11-1-makefile-updates). Affects: AM243x & AM64x MCU+ cores

Evidence

The link is authored with an explicit fragment "#7-revert-mcu-sdk-11-1-makefile-updates" but the
only target section is the H2 header text containing "11.1" (with a dot). Since there is no explicit
anchor ID defined in the markdown, correct navigation depends on how the renderer converts "11.1"
into an ID. The repo already demonstrates elsewhere that dotted version headers are linked by
removing dots (e.g., "v2026.00.00" -> "#v20260000"), which suggests the same dot-removal behavior
may apply here and make "11-1" not match.

docs/using_older_sdks_with_open_pru.md[95-99]
docs/using_older_sdks_with_open_pru.md[189-194]
docs/release_notes.md[9-13]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The internal link to section 7 uses a fragment identifier containing `11-1`, but the destination header contains `11.1`. Because there is no explicit HTML anchor, the link depends on markdown renderer auto-ID rules and may not navigate correctly.

### Issue Context
- Link: `[7. ...](#7-revert-mcu-sdk-11-1-makefile-updates)`
- Destination header: `## 7. Revert MCU+ SDK 11.1 makefile updates`

### Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[95-99]
- docs/using_older_sdks_with_open_pru.md[189-190]

### Suggested fix options
1) **Stable explicit anchor** (most robust across renderers):
  - Add an explicit anchor before the header, e.g.:
    - `&lt;a id=&quot;7-revert-mcu-sdk-11-1-makefile-updates&quot;&gt;&lt;/a&gt;`
  - Keep the existing link fragment as-is.

2) **Match GitHub-style auto ID**:
  - Change the link fragment to the actual auto-generated header ID (likely dot-removed), e.g. `#7-revert-mcu-sdk-111-makefile-updates` if using GitHub-style dot stripping.
  - Prefer option (1) if you want to avoid relying on auto-ID conventions.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

5. Duplicate Release Notes header 🐞 Bug ✓ Correctness

Description

The file now has both an H1 and an H2 named "Release Notes", so the TOC link #release-notes will
land on the top H1 instead of the versioned section header (GitHub disambiguates duplicates by
appending -1). This degrades navigation and makes the TOC misleading.

Code

docs/release_notes.md[R40-43]
+## Release Notes
+
+### v2026.00.00
+

Evidence

The TOC links #release-notes, but there are two headings with the same text; the later one is the
actual start of the versioned notes, so the link target will not match reader intent.

docs/release_notes.md[5-13]
docs/release_notes.md[40-43]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains both `# Release Notes` and `## Release Notes`. The TOC entry `[Release Notes](#release-notes)` will navigate to the first heading (the H1), not the section where versioned release notes begin.
### Issue Context
GitHub generates the same slug for same-text headings and disambiguates subsequent duplicates (e.g., `release-notes-1`). This makes the current TOC link misleading.
### Fix Focus Areas
- docs/release_notes.md[9-13]
- docs/release_notes.md[40-43]
### Suggested direction
- Option A (preferred): Rename the H2 to something unique like `## Release Notes by Version` and update the TOC link accordingly.
- Option B: Remove the `## Release Notes` H2 entirely and let the TOC jump directly to `v2026.00.00` / `v2025.00.00`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

6. PR linked as commit 🐞 Bug ✓ Correctness

Description

The new older-SDK guidance says "OpenPRU commit" but links to a GitHub pull request URL. This can
confuse readers looking for an exact commit to revert (or whether they should revert a series of
changes).

Code

+In order to undo these changes, revert the file changes that were done in
+OpenPRU commit
+[AM243x & AM64x: Add support for MCU+ SDK 11.1&11.2](https://github.com/TexasInstruments/open-pru/pull/110)

Evidence

The wording explicitly says "commit" while the URL clearly points to /pull/110 (a PR), creating a
terminology/link mismatch.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The doc says &amp;quot;OpenPRU commit&amp;quot; but links to a pull request (`/pull/110`). This mismatch can confuse users following revert instructions.
### Issue Context
A PR link may be intentional/preferable (it provides full context and may include multiple commits). If so, the text should call it a PR/changes introduced in the PR.
### Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[197-199]
### Suggested direction
- Change wording to e.g. &amp;quot;revert the file changes introduced in OpenPRU PR #110&amp;quot;.
- If you want a single commit reference, replace the link with the specific commit URL and keep &amp;quot;commit&amp;quot;.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

7. FIR typo in notes 🐞 Bug ✓ Correctness

Description

The FIR example description misspells "Response" as "Respose". This reduces doc quality and makes
searching for the term harder.

Code

+* Add examples/fir
+  * Implement 64-tap Finite Impulse Respose (FIR) filter on PRU
+  * supports AM243x

Evidence

The added bullet contains a spelling error in a technical term (FIR stands for Finite Impulse
Response).

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The release notes text for the FIR example has a typo: &amp;quot;Respose&amp;quot; instead of &amp;quot;Response&amp;quot;.
### Issue Context
FIR is a standard acronym for *Finite Impulse Response*; the typo also reduces searchability.
### Fix Focus Areas
- docs/release_notes.md[85-87]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Results up to commit b3cc750

🐞 Bugs (3) 📘 Rule violations (1) 📎 Requirement gaps (0)

1. Unwrapped academy URLs exceed limit 📘 Rule violation ✓ Correctness

Description

docs/release_notes.md includes long unwrapped markdown link lines that likely exceed the
129-column hard limit. This violates the repository formatting rules and can reduce diff readability
and portability across tools.

Code

docs/release_notes.md[5-13]
docs/release_notes.md[40-43]

+[PRU Academy for AM243x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM24X-ACADEMY__ZPSnq-h__LATEST)  
+[PRU Academy for AM64x](https://dev.ti.com/tirex/explore/node?isTheia=false&node=A__AB.mSUi9ihL.a5hIt1grfw__AM64-ACADEMY__WI1KRXP__LATEST)

Evidence
Compliance rule 16 requires lines to generally stay within 79 columns and never exceed 129 columns;
the newly added academy link lines contain very long URLs on a single line, exceeding the hard
limit.
docs/release_notes.md[69-70]
docs/release_notes.md[131-132]
Best Practice: Repository guidelines

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/release_notes.md` contains newly added markdown link lines with long URLs that exceed the 129-column hard limit.

## Issue Context
Compliance requires lines to generally stay within 79 columns and never exceed 129 columns.

## Fix Focus Areas
- docs/release_notes.md[69-70]
- docs/release_notes.md[131-132]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Duplicate Release Notes header 🐞 Bug ✓ Correctness

Description

The file now has both an H1 and an H2 named "Release Notes", so the TOC link #release-notes will
land on the top H1 instead of the versioned section header (GitHub disambiguates duplicates by
appending -1). This degrades navigation and makes the TOC misleading.

Code

docs/release_notes.md[R40-43]
+## Release Notes
+
+### v2026.00.00
+

Evidence

The TOC links #release-notes, but there are two headings with the same text; the later one is the
actual start of the versioned notes, so the link target will not match reader intent.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`docs/release_notes.md` contains both `# Release Notes` and `## Release Notes`. The TOC entry `[Release Notes](#release-notes)` will navigate to the first heading (the H1), not the section where versioned release notes begin.

### Issue Context
GitHub generates the same slug for same-text headings and disambiguates subsequent duplicates (e.g., `release-notes-1`). This makes the current TOC link misleading.

### Fix Focus Areas
- docs/release_notes.md[9-13]
- docs/release_notes.md[40-43]

### Suggested direction
- Option A (preferred): Rename the H2 to something unique like `## Release Notes by Version` and update the TOC link accordingly.
- Option B: Remove the `## Release Notes` H2 entirely and let the TOC jump directly to `v2026.00.00` / `v2025.00.00`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. PR linked as commit 🐞 Bug ✓ Correctness

Description

The new older-SDK guidance says "OpenPRU commit" but links to a GitHub pull request URL. This can
confuse readers looking for an exact commit to revert (or whether they should revert a series of
changes).

Code

+In order to undo these changes, revert the file changes that were done in
+OpenPRU commit
+[AM243x & AM64x: Add support for MCU+ SDK 11.1&11.2](https://github.com/TexasInstruments/open-pru/pull/110)

Evidence

The wording explicitly says "commit" while the URL clearly points to /pull/110 (a PR), creating a
terminology/link mismatch.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The doc says &quot;OpenPRU commit&quot; but links to a pull request (`/pull/110`). This mismatch can confuse users following revert instructions.

### Issue Context
A PR link may be intentional/preferable (it provides full context and may include multiple commits). If so, the text should call it a PR/changes introduced in the PR.

### Fix Focus Areas
- docs/using_older_sdks_with_open_pru.md[197-199]

### Suggested direction
- Change wording to e.g. &quot;revert the file changes introduced in OpenPRU PR #110&quot;.
- If you want a single commit reference, replace the link with the specific commit URL and keep &quot;commit&quot;.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

4. FIR typo in notes 🐞 Bug ✓ Correctness

Description

The FIR example description misspells "Response" as "Respose". This reduces doc quality and makes
searching for the term harder.

Code

+* Add examples/fir
+  * Implement 64-tap Finite Impulse Respose (FIR) filter on PRU
+  * supports AM243x

Evidence

The added bullet contains a spelling error in a technical term (FIR stands for Finite Impulse
Response).