Merge pull request #799 from gal-revach:patch-22

Updating the section for API support policy after legal comments

Author: jasonnovichRunAI

docs/developer/overview-developer.md

@@ -10,9 +10,9 @@ Developers can access Run:ai through various programmatic interfaces.
 
 ## API Support
 
-The endpoints and parameters specified in the API reference are the ones that are officially supported by Run:ai. Endpoints and parameters that are **NOT** listed in the reference are not officially supported.
+The endpoints and fields specified in the [API reference](https://app.run.ai/api/docs) are the ones that are officially supported by Run:ai. Endpoints and fields that are not listed in the API reference are not supported.
 
-API endpoints and fields marked as `deprecated` remain operational and can be used; however, Run:ai will **NO LONGER RECOMMEND USING THEM**, **WILL NOT ADD FUNCTIONALITY TO THEM**, and **WILL STOP SUPPORTING THEM** after 2 major releases (for self-hosted deployments), and after 6 months of support for SaaS deployments.
+Run:ai does not recommend using API endpoints and fields marked as `deprecated` and will not add functionality to them. Once an API endpoint or field is marked as `deprecated`, Run:ai will stop supporting it after 2 major releases for self-hosted deployments, and after 6 months for SaaS deployments.
 
 For details, see the [Deprecation notifications](../home/whats-new-2-17.md#deprecation-notifications).