Merge pull request #1413 from swirlai/moredocfixes

Moredocfixes
swirlai · Aug 21, 2024 · 9ef0326 · 9ef0326
2 parents e99a066 + 2a15d3e
commit 9ef0326
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 6 deletions.
diff --git a/docs/Developer-Guide.md b/docs/Developer-Guide.md
@@ -444,7 +444,7 @@ If you need more mixed results, increase the `results_per_query` value in the Se
 SWIRL reports each source's search time in the relevant `info` block of the response:
 
 ``` json
-        "info": "Enterprise Search (web/Google PSE)": {
+        "info": "Web (Google PSE)": {
             "found": 8640,
             "retrieved": 10,
             ...
@@ -529,7 +529,7 @@ The structure also includes matching stems (`"stems"`), result and query length
 ## Develop New Connectors
 
 {: .warning }
-To connect to a new endpoint for an existing Connector - like RequestsGet - create a new SearchProvider instead. The [Google PSE SearchProvider example JSON](https://github.com/swirlai/swirl-search/blob/main/SearchProviders/google_pse.json) shows how to use one connector to make hundreds of SearchProviders!
+To connect to a new endpoint for an existing Connector - like RequestsGet - create a new SearchProvider instead. The [Google PSE SearchProvider example JSON](https://github.com/swirlai/swirl-search/blob/main/SearchProviders/google.json) shows how to use one connector to make hundreds of SearchProviders!
 
 To search against a new API where there is a high quality Python package and/or a unique data transport not already supported - then write a new Connector. 
 
@@ -863,7 +863,7 @@ Update the Search Provider's `query_processors` field to include the reference.
 
 ``` json
 {
-    "name": "TEST Enterprise Search (web/Google PSE) with qxr query_processor",
+    "name": "TEST Web (Google PSE) with qxr query_processor",
     "active": "true",
     "default": "true",
     "connector": "RequestsGet",

diff --git a/docs/M365-Guide.md b/docs/M365-Guide.md
@@ -14,9 +14,7 @@ nav_order: 14
 
 # Microsoft 365 Guide
 
-## Intended Audience
-
-This guide details how to integrate SWIRL (v. 2.0 or newer) with an existing Microsoft 365 (M365) tenant. It is intended for use by M365 Administrators with authority to add a new App Registration in their Azure Portal and optionally grant permissions for various APIs as noted below on behalf of users who wish to use SWIRL to query their personal M365 content.
+This guide details how to integrate SWIRL with an existing Microsoft 365 (M365) tenant. It is intended for use by M365 Administrators with authority to add a new App Registration in their Azure Portal and optionally grant permissions for various APIs as noted below on behalf of users who wish to use SWIRL to query their personal M365 content.
 
 # Register a New App in Azure Portal