docs: drop the duplicated feature list from the README by JeanExtreme002 · Pull Request #90 · JeanExtreme002/PyMemoryEditor

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 · 2026-08-28T20:59:19Z

Why is this PR necessary, what does it do?

Removes the "What's inside" section from the README.

It listed the library's capabilities and the GUI app's, and the Documentation
table immediately below it already points at every one of them — searching,
pattern scan, pointers, pointer scan, the app, the API reference. Two lists of
the same thing drift apart, and the one that goes stale is the one nobody
remembers to edit when a feature lands.

The README keeps what only it can do: what the project is, how to install it,
and the three-line example.

Checklist (complete all items):

Added tests as necessary.
There is no breaking change for existing features.

References:

No references to be shared.

Notes:

Nothing links to the removed section — no #whats-inside anchor anywhere in
README.md, docs/ or .github/. (docs/app.md has a heading with the same
name, but it is that file's own section and is not referenced from outside it.)
The surrounding text still reads continuously: example → "That's it — read,
write or scan another process in three lines" → Documentation.

The "What's inside" section listed the library's capabilities and the GUI app's, both of which the Documentation table right below it already points at — searching, pattern scan, pointers, pointer scan, the app, the API reference. Two lists of the same thing drift apart, and the one that goes stale is the one nobody edits when a feature lands. The README keeps what only it can do: what the project is, how to install it, and a three-line example.

JeanExtreme002 merged commit 3c92c23 into mainAug 28, 2026
13 checks passed

github-actionsBot deleted the docs/readme-trim-features branch August 28, 2026 21:02