Update README.md

README.md

@@ -189,9 +189,14 @@ Please refer to the documentation of SerpApi's Google Local API and Google Local
   <div style="display: flex; justify-content: center;">
     <div style="text-align: left;">
       <ul style="list-style-position: inside;">
-        <li>Button text like "Delivery" could be considered <code>service_options</code>. However, this can be easily avoided by checking if a text is in a button in the traditional part of the code. The button text is only used for emergency cases.</li>
         <li>The model does not classify the title of a place. This is because the title often contains many elements that can be easily confused with other parts, even for a human eye.</li>
         <li>The <code>label</code> key is not covered by the model, as it can be easily handled with traditional code.</li>        
+        <li>In some cases, <code>button text</code> could be classified as <code>service options</code> or <code>address</code>. However, this can be easily avoided by checking if a text is in a button in the traditional part of the code. The button text is only used to prevent emergent cases.
+          <ul style="list-style-type: circle">
+            <li><code>"Delivery"</code> &rarr; <code>service options [Correct Label is button text]</code></li>
+            <li><code>"Share"</code> &rarr; <code>address [Correct Label is button text]</code></li>
+          </ul>
+        </li>
         <li>In some cases, the model may classify a portion of the <code>description</code> as <code>hours</code> if the description is about operating hours. For example:
           <ul style="list-style-type: disc;">
             <li><code>"Drive through: Open ⋅ Closes 12 AM"</code>
@@ -202,7 +207,7 @@ Please refer to the documentation of SerpApi's Google Local API and Google Local
             </li>
           </ul>
         </li>
-        <li>In some cases, the model may classify some <code>description</code> as <code>type</code>. This is because some description do look like type. For Example:
+        <li>In some cases, the model may classify some <code>description</code> as <code>type</code>. This is because some <code>description</code> do look like <code>type</code>. For Example:
           <ul style="list-style-type: circle">
             <li><code>"Iconic Seattle-based coffeehouse chain"</code> &rarr; <code>type [Correct Label is description]</code></li>
           </ul>
@@ -217,12 +222,19 @@ Please refer to the documentation of SerpApi's Google Local API and Google Local
             <li><code>"Takeaway"</code> &rarr; <code>type [Correct Label is service options]</code></li>
           </ul>
         </li>
-        <li>In some cases, the model may classify some <code>button text</code> as <code>hours</code>. This is most likely a deficiency in the training dataset, and may be resolved in the coming versions. For Example:
+        <li>In some cases, the model may classify some <code>reviews</code> as <code>hours</code> or <code>price</code>. This is most likely a deficiency in the training dataset, and may be resolved in the coming versions. For Example:
           <ul style="list-style-type: circle">
             <li><code>"(1.4K)"</code> &rarr; <code>rating [Correct Label is reviews]</code></li>
+            <li><code>"(1.6K)"</code> &rarr; <code>price [Correct Label is reviews]</code></li>
+          </ul>
+        </li>
+        <li>In some cases, the model may classify some <code>service options</code> as <code>description</code> or <code>type</code>. The reason for the confusion on <code>description</code> is because of a recent change in their categorization in SerpApi keys. The data contains labels prior to that. For Example:
+          <ul style="list-style-type: circle">
+            <li><code>"On-site services"</code> &rarr; <code>type [Correct Label is service options]</code></li>
+            <li><code>"Online appointments"</code> &rarr; <code>description [Correct Label is service options]</code></li>
           </ul>
         </li>
-        <li>The model may be susceptible to error in one word entries. This is a minority of the cases, and it could be fixed with assurance scores.For Example:
+        <li>The model may be susceptible to error in one word entries. This is a minority of the cases, and it could be fixed with assurance scores. For Example:
           <ul style="list-style-type: circle">
             <li><code>"Sushi"</code> &rarr; <code>address(0.984), type(0.0493) [Correct Label is type]</code></li>
             <li><code>"Diagorou 4"</code> &rarr; <code>address(0.999) [Correct address in same listing]</code></li>