(arrow) branch main updated: MINOR: [C++] Fix a typo in the doc of `pyarrow.compute.ascii_upper` (#48700)

[kou]

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

kou pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow.git


The following commit(s) were added to refs/heads/main by this push:
     new f9dd729194 MINOR: [C++] Fix a typo in the doc of  
`pyarrow.compute.ascii_upper` (#48700)
f9dd729194 is described below

commit f9dd7291947d90a0035968f58fe04f2df1a4cf7b
Author: Ruifeng Zheng <ruife...@foxmail.com>
AuthorDate: Wed Dec 31 19:31:23 2025 -0800

    MINOR: [C++] Fix a typo in the doc of  `pyarrow.compute.ascii_upper` 
(#48700)
    
    ### Rationale for this change
    in existing 
https://arrow.apache.org/docs/dev/python/generated/pyarrow.compute.ascii_upper.html
    
    > This function assumes the input is fully ASCII. It it may contain 
non-ASCII characters, use “utf8_upper” instead.
    
    ### What changes are included in this PR?
    Fix a typo in the docstring of  `pyarrow.compute.ascii_upper`
    
    ### Are these changes tested?
    CI
    
    ### Are there any user-facing changes?
    yes, doc-only change
    
    Authored-by: Ruifeng Zheng <ruife...@apache.org>
    Signed-off-by: Sutou Kouhei <k...@clear-code.com>
---
 cpp/src/arrow/compute/kernels/scalar_string_ascii.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cpp/src/arrow/compute/kernels/scalar_string_ascii.cc 
b/cpp/src/arrow/compute/kernels/scalar_string_ascii.cc
index 06e6f4bb50..dd5abed16c 100644
--- a/cpp/src/arrow/compute/kernels/scalar_string_ascii.cc
+++ b/cpp/src/arrow/compute/kernels/scalar_string_ascii.cc
@@ -804,7 +804,7 @@ using AsciiTitle = StringTransformExec<Type, 
AsciiTitleTransform>;
 const FunctionDoc ascii_upper_doc(
     "Transform ASCII input to uppercase",
     ("For each string in `strings`, return an uppercase version.\n\n"
-     "This function assumes the input is fully ASCII.  It it may contain\n"
+     "This function assumes the input is fully ASCII.  If it may contain\n"
      "non-ASCII characters, use \"utf8_upper\" instead."),
     {"strings"});