Part 3: Third fourth content unordered lists from dash to asterisk (#51097)

content/search-github/github-code-search/about-github-code-search.md

@@ -32,14 +32,14 @@ We have indexed many public repositories for code search, and continue to index
 
 The current limitations on indexed code are:
 
-- Vendored and generated code is excluded
-- Empty files and files over 350 KiB are excluded
-- Lines over 1,024 characters long are truncated
-- Binary files (PDF, etc.) are excluded
-- Only UTF-8 encoded files are included
-- Very large repositories may not be indexed
-- Exhaustive search is not supported
-- Files with more than one line over 4096 bytes are excluded
+* Vendored and generated code is excluded
+* Empty files and files over 350 KiB are excluded
+* Lines over 1,024 characters long are truncated
+* Binary files (PDF, etc.) are excluded
+* Only UTF-8 encoded files are included
+* Very large repositories may not be indexed
+* Exhaustive search is not supported
+* Files with more than one line over 4096 bytes are excluded
 
 We currently only support searching for code on the default branch of a repository. The query length is limited to 1000 characters.
 

content/search-github/github-code-search/understanding-github-code-search-syntax.md

@@ -98,13 +98,13 @@ You can use parentheses to express more complicated boolean expressions. For exa
 ## Using qualifiers
 
 You can use specialized keywords to qualify your search.
-- [Repository qualifier](#repository-qualifier)
-- [Organization and user qualifiers](#organization-and-user-qualifiers)
-- [Language qualifier](#language-qualifier)
-- [Path qualifier](#path-qualifier)
-- [Symbol qualifier](#symbol-qualifier)
-- [Content qualifier](#content-qualifier)
-- [Is qualifier](#is-qualifier)
+* [Repository qualifier](#repository-qualifier)
+* [Organization and user qualifiers](#organization-and-user-qualifiers)
+* [Language qualifier](#language-qualifier)
+* [Path qualifier](#path-qualifier)
+* [Symbol qualifier](#symbol-qualifier)
+* [Content qualifier](#content-qualifier)
+* [Is qualifier](#is-qualifier)
 
 ### Repository qualifier
 
@@ -191,13 +191,13 @@ To search for JavaScript files within a `src` directory, you could use:
 path:src/*.js
 ```
 
-- By default, glob expressions are not anchored to the start of the path, so the above expression would still match a path like `app/src/main.js`. But if you prefix the expression with `/`, it will anchor to the start. For example:
+* By default, glob expressions are not anchored to the start of the path, so the above expression would still match a path like `app/src/main.js`. But if you prefix the expression with `/`, it will anchor to the start. For example:
 
     ```text
     path:/src/*.js
     ```
 
-- Note that `*` doesn't match the `/` character, so for the above example, all results will be direct descendants of the `src` directory. To match within subdirectories, so that results include deeply nested files such as `/src/app/testing/utils/example.js`, you can use `**`. For example:
+* Note that `*` doesn't match the `/` character, so for the above example, all results will be direct descendants of the `src` directory. To match within subdirectories, so that results include deeply nested files such as `/src/app/testing/utils/example.js`, you can use `**`. For example:
 
     ```text
     path:/src/**/*.js
@@ -258,10 +258,10 @@ This query would only match files containing the term `README.md`, rather than m
 
 To filter based on repository properties, you can use the `is:` qualifier. `is:` supports the following values:
 
-- `archived`: restricts the search to archived repositories.
-- `fork`: restricts the search to forked repositories.
-- `vendored`: restricts the search to content detected as vendored.
-- `generated`: restricts the search to content detected as generated.
+* `archived`: restricts the search to archived repositories.
+* `fork`: restricts the search to forked repositories.
+* `vendored`: restricts the search to content detected as vendored.
+* `generated`: restricts the search to content detected as generated.
 
 For example:
 

content/search-github/github-code-search/using-github-code-search.md

@@ -45,8 +45,8 @@ For more information about the search syntax of code search, see "[AUTOTITLE](/s
 1. To finish creating your saved search, click **Create saved search**.
 1. To see your saved search, click the search bar. Your saved search will be in the "Saved queries" section. Clicking on a saved search entry will add the query to the search bar and filter the suggestions accordingly.
 1. To manage a saved search, type `saved:` in the search bar, then click {% octicon "plus-circle" aria-hidden="true" %} **Manage saved searches**.
-    - To edit a saved search, to the right of the search, click {% octicon "pencil" aria-label="The pencil icon" %}.
-    - To delete a saved search, to the right of the search, click {% octicon "trash" aria-label="The trash icon" %}.
+    * To edit a saved search, to the right of the search, click {% octicon "pencil" aria-label="The pencil icon" %}.
+    * To delete a saved search, to the right of the search, click {% octicon "trash" aria-label="The trash icon" %}.
 
 ## Using the search results view