# Unexpected Search Behavior: When 'commands' Doesn't Find '/commands'

**URL:** <https://meta.discourse.org/t/unexpected-search-behavior-when-commands-doesnt-find-commands/315217>\
**Category:** Bug\
**Tags:** search\
**Created:** [July 6, 2024, 4:27am UTC](https://meta.discourse.org/t/unexpected-search-behavior-when-commands-doesnt-find-commands/315217 "2024-07-06T04:27:02Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![MarcP](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/marcp/32/160184_2.png) [@MarcP](https://meta.discourse.org/u/MarcP)\
**Post date:** [August 12, 2024, 9:17pm UTC](https://meta.discourse.org/t/unexpected-search-behavior-when-commands-doesnt-find-commands/315217/6 "2024-08-12T21:17:14Z")

</div>

> [@j.jaffeux](#):
>
> We just failed to find `commands`, which we could debate it should find, but it’s not a bug per say.

Right, I do not expect my users to know upfront that they need to include “/” to find this. Any reason why this behaviour is expected or a possible workaround? Because it seriously affects the search-ability of my documentation.

---

_[View the full topic](https://meta.discourse.org/t/unexpected-search-behavior-when-commands-doesnt-find-commands/315217)._