We've now gotten a fair number of "cheatsheet" entries in the books list. I'd like to propose that we move these to a separate page.

Reasons:

1. Will be easier to find cheatsheets
2. Cheatsheets aren't books
3. Cheat sheets aren't so spoken-language specific.
4. The english-language books page is getting long.
5. Will encourage better cheatsheet coverage.

Against:

1. Scope creep.

As discussed at TheAlgorithms/Python#3934 (comment)

There's also greedy_knapsack in the greedy_method directory.

Proposal:

• Remove images and greedy_method directory.
• Move greedy_knapsack to knapsack directory as there are multiple variations for the knapsack problem according to [Wikipedia](https://en.wikipedia.org/wiki/Knapsack_problem#

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Right now (at least if you use multiple) Autocomplete/useAutocomplete the value that comes back in onChange is always the raw option data. i.e. If you use options=[{value: 'a', label: 'A'}, {value: 'b', label: 'B'}] and select the

Proof read transcribed code of UPDATE_PROGRAM against scans

Lines: 548
Page: 1386—1396 (10)

Reduced quality scans can be found here

It is currently expected that UIs will figure out when to hide msg_history_show messages by themselves.

I think this is bad for two reasons:

• It makes UIs less similar, increasing the number of things to learn when going from one UI to another.
• It makes UIs different from the TUI, which offers a press ENTER prompt when the time to hide msg_history_show messages has come.

After [di

Some of the links like cryptography installation in file install.rst are outdated and require an update.
It will be nice to check for other parts of the documentation for the same issue.

What would you like to be added:

Currently, some headings are also steps in procedures. The format is not consistent. We need the heading format made consistent per the Grafana documentation style guide.

This means both the step number format (Step 1., Step 2.) and that everyt

Related PR: #6331
Suggested by @pimlie

When trailing slash handling is enforced (in any manner), it'd be great to have two things for improved DX:

Nuxt Link adaption

No matter how you input the links in your Nuxt link (be it as an object via named routes or via string), the component should enforce the set up trailing slash handling (adding or removing the slashes as needed).

U