Doc typos and updates

Author: robertlazarski

src/site/xdoc/docs/json-springboot-userguide.xml

@@ -68,8 +68,7 @@ prefix the subject of the mail with [Axis2].</p>
 <h2>Getting Started</h2>
 
 <p>This user guide explains how to write and deploy a
-new JSON and REST based Web Service using Axis2, and how to write a Web Service client 
-using JSON with Curl.
+new JSON and REST based Web Service using Axis2, and how to invoke a Web Service client using JSON with Curl.
 </p>
 
 <p>All the sample code mentioned in this guide is located in
@@ -150,7 +149,7 @@ that registers AxisServlet with Spring Boot 3.
 </p>
 <p>
 Axis2 web services are installed via a WEB-INF/services directory that contains
-files with an .aar extention for each service. These aar files are similar to
+files with an .aar extension for each service. These aar files are similar to
 jar files, and contain a services.xml that defines the web service behavior. 
 The pom.xml supplied in this guide generates these files.
 </p>

src/site/xdoc/docs/json_support_gson.xml

@@ -101,9 +101,9 @@
             <p>With this approach you can expose your POJO service to accept pure JSON request other than converting to
                 any representation or format. You just need to send a valid JSON string request to the service url and,
                 in the url you should have addressed the operation as well as the service. Because in this scenario Axis2
-                uses URI based operation dispatcher to dispatch the correct operation. in
+                uses URI based operation dispatcher to dispatch the correct operation. In the docs
                 <a href="json_gson_user_guide.html#native_approach">here</a> you can
-                find the complete user guide for this native approach.</p>
+                find the guide for setting up this native approach, while <a href="json-springboot-userguide.html">here</a> you can find a complete Native Approach example for the client and server with a Spring Boot 3 sample application. </p>
 
             <p>The Native approach is being implemented to use pure JSON throughout the axis2 message processing
                 process. In Axis2 as the content-type header is used to specify the type of data in the message body,