diff --git a/content/github/searching-for-information-on-github/searching-on-github/searching-code.md b/content/github/searching-for-information-on-github/searching-on-github/searching-code.md
index 2567672360..3fed9dd86c 100644
--- a/content/github/searching-for-information-on-github/searching-on-github/searching-code.md
+++ b/content/github/searching-for-information-on-github/searching-on-github/searching-code.md
@@ -33,7 +33,7 @@ Due to the complexity of searching code, there are some restrictions on how sear
 - Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %}
 - Except with [`filename`](#search-by-filename) searches, you must always include at least one search term when searching source code. For example, searching for [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) is not valid, while [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) is.
 - At most, search results can show two fragments from the same file, but there may be more results within the file.
-- You can't use the following wildcard characters as part of your search query: <code>. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ]</code>. The search will simply ignore these symbols.
+- You can't use the following wildcard characters as part of your search query: <code>. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @</code>. The search will simply ignore these symbols.
 
 ### Search by the file contents or file path