Update content/packages-and-modules/getting-packages-from-the-registry/searching-for-and-choosing-packages-to-download.mdx

Updating to suggestions from @leobalter

Co-authored-by: Leo Balter <[email protected]>

Author: monishcm

content/packages-and-modules/getting-packages-from-the-registry/searching-for-and-choosing-packages-to-download.mdx

@@ -4,7 +4,9 @@ redirect_from:
   - /getting-started/searching-for-packages
 ---
 
-You can use the npm search bar to locate packages for your projects. The search function leverages information from a package's title, description, readme, and keywords, powered by OpenSearch. Results are displayed based on keyword matching from these fields, without subjective ranking criteria. However, adjustments are applied to deprioritise spammy or recently published packages to ensure search neutrality. Please note that newly published packages may take up to one-two week to appear in the search results. Additionally, deprecated packages are excluded from the search results to enhance the user experience.
+You can use the npm search bar to find packages to use in your projects. The search is performed using content from the package's title, description, readme, and keywords and is powered by [opensearch](https://opensearch.org/). Search results are displayed based on keyword matching from the package's title, description, readme, and keywords. No subjective ranking criteria are applied, except for a minimal boost to deprioritize spammy or entirely new packages, aiming to maintain a neutral stance towards all other packages.
+
+Please note that newly published packages may take up to one-two week to appear in the search results. Additionally, deprecated packages are excluded from the search results to enhance the user experience.
 
 ## Searching for a package