This is an automated email from the ASF dual-hosted git repository.

mihaibudiu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/calcite-avatica.git


The following commit(s) were added to refs/heads/main by this push:
     new e2e959e06 Fix typo 'dependecies' to 'dependencies' in 
custom_client_artifacts.md
e2e959e06 is described below

commit e2e959e06b4f541cae4766152e3fb42e42ca00d8
Author: Mohd Irshad <[email protected]>
AuthorDate: Thu Nov 5 20:35:07 2026 +0530

    Fix typo 'dependecies' to 'dependencies' in custom_client_artifacts.md
    
    Signed-off-by: siddiqueirshad <[email protected]>
---
 site/_docs/custom_client_artifacts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/_docs/custom_client_artifacts.md 
b/site/_docs/custom_client_artifacts.md
index f128a4f42..8be0d1e09 100644
--- a/site/_docs/custom_client_artifacts.md
+++ b/site/_docs/custom_client_artifacts.md
@@ -48,7 +48,7 @@ can be safely relocated are done so to reduce the potential 
for classpath issues
 Avatica 1.9.0 will introduce a new artifact 
`org.apache.calcite.avatica:avatica-core` which is only
 the Avatica client classes without any bundled dependencies. This artifact 
enables users to build a
 classpath with different versions of JARs than what Avatica presently depends 
upon. This is a "your-mileage-may-vary"
-or "void-your-warranty" type of decision (as you are using Avatica with 
dependecies which we have not tested);
+or "void-your-warranty" type of decision (as you are using Avatica with 
dependencies which we have not tested);
 however, some downstream projects do provide reasonable assurances of 
compatibilities across releases.
 
 ## Building your own Avatica client artifact

Reply via email to