From 07c325fdaeb7c3ad5530caba7a5b408cdb36431a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Timo=20Westk=C3=A4mper?= <timo.westkamper@nosto.com>
Date: Fri, 1 Nov 2024 10:43:15 +0200
Subject: [PATCH] Remove deprecated name parameter

---
 .../implementing-category-pages.md                     | 10 ++++------
 .../implementing-search-page.md                        |  3 ---
 2 files changed, 4 insertions(+), 9 deletions(-)

diff --git a/implementing-nosto/implement-search/getting-started-with-nosto-search/implementing-category-pages.md b/implementing-nosto/implement-search/getting-started-with-nosto-search/implementing-category-pages.md
index 47a3795..8c09bd2 100644
--- a/implementing-nosto/implement-search/getting-started-with-nosto-search/implementing-category-pages.md
+++ b/implementing-nosto/implement-search/getting-started-with-nosto-search/implementing-category-pages.md
@@ -21,7 +21,6 @@ init({
     categoryCssSelector: '#MainContent',
 
     categoryQuery: {
-      name: 'serp',
       products: {
         categoryId: "1234567",
         categoryPath: "dresses",
@@ -35,7 +34,7 @@ init({
 
 #### categoryQuery parameter as function&#x20;
 
-In the example above, we supply autocomplete query parameters as an object. Additionally, categoryQuery parameters can also be supplied as a function. The function flavor can be used for building complex query parameters and provides access to other pre-defined configuration parameters. Section below shows an example of categoryQuery supplied as a function which provides the  product variationId by accessing the pre-defined categoryId() and categoryPath() methods from the default configuration.
+In the example above, we supply autocomplete query parameters as an object. Additionally, categoryQuery parameters can also be supplied as a function. The function flavor can be used for building complex query parameters and provides access to other pre-defined configuration parameters. Section below shows an example of categoryQuery supplied as a function which provides the  product variationId by accessing the pre-defined `categoryId` and `categoryPath` methods from the default configuration.
 
 ```javascript
 import { init } from '@nosto/preact'
@@ -50,7 +49,6 @@ init({
 
     categoryQuery: () => {
         return {
-          name: 'serp',
           products: {
             categoryId: this.categoryId(),
             categoryPath: this.categoryPath(),
@@ -65,11 +63,11 @@ init({
 {% hint style="info" %}
 If you want to integrate only Categories without Search or Autocomplete, ensure that the following entries are removed or commented out:&#x20;
 
-serpComponent
+`serpComponent`
 
-historyComponent
+`historyComponent`
 
-autocompleteComponent
+`autocompleteComponent`
 {% endhint %}
 
 ### Handling native results
diff --git a/implementing-nosto/implement-search/implement-search-using-code-editor/implementing-search-page.md b/implementing-nosto/implement-search/implement-search-using-code-editor/implementing-search-page.md
index 8a52de1..c7f6bef 100644
--- a/implementing-nosto/implement-search/implement-search-using-code-editor/implementing-search-page.md
+++ b/implementing-nosto/implement-search/implement-search-using-code-editor/implementing-search-page.md
@@ -21,7 +21,6 @@ init({
         query: 'q',
     },
     serpQuery: {
-        name: 'serp',
         products: {
             size: 20,
             from: 0,
@@ -52,7 +51,6 @@ init({
     },
     serpQuery() {
         return {
-            name: 'serp',
             products: {
                 size: 20,
                 from: 0,
@@ -129,7 +127,6 @@ init({
     },
     compressUrlParameters: true,
     serpQuery: {
-        name: 'serp',
         products: {
             size: 20,
             from: 0,