chore: more words

configuration/analytics.mdx

@@ -25,14 +25,17 @@ The image above shows the past 30 minutes of the flag `flag1` evaluation counts.
 
 ### Database
 
-It's important to note that we do \*recommend\*\* to use a separate database for analytics produced by Flipt. This ensures that Flipt analytic data can be logically isolated from the rest of your Clickhouse data.
+We highly **recommend** using a separate database for analytics produced by Flipt. This ensures that Flipt analytic data can be logically isolated from the rest of your Clickhouse data.
 
 <Note>
-The analytics database must be created before Flipt will be able to write analytical data and run any migrations. See our [migration](https://www.flipt.io/docs/configuration/storage#migrations) section for more info.
+  The analytics database must be created before Flipt will be able to write
+  analytical data and run any migrations. See our
+  [migration](https://www.flipt.io/docs/configuration/storage#migrations)
+  section for more info.
 </Note>
 
 ### Origin of Analytics
 
 Analytics are currently only collected as they pass through the evaluation server. This means that analytics will be captured if you are using the REST or GRPC APIs via one of our [Server SDKs](/integration/server/rest) or [GRPC SDKs](/integration/server/grpc) for evaluations.
 
-We have plans to support collecting analytics for client-side evaluations in the future.
+We have plans to support collecting analytics for [Client-Side](/integration/client) evaluations in the future.