[QPROF] Enhancement + misc

- Rewriting some definition. - Should close:
vertica · Oct 4, 2024 · a58bb45 · a58bb45
1 parent d70b7b2
commit a58bb45
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 15 deletions.
diff --git a/verticapy/core/vdataframe/_plotting.py b/verticapy/core/vdataframe/_plotting.py
@@ -253,8 +253,8 @@ def bar(
                 (ex: 50% to get the median).
             - None:
                 No Aggregations. Parameter ``of``
-                must not be empty, otherwise it
-                is ignored.
+                must be empty, otherwise it is
+                ignored.
 
             It can also be a cutomized aggregation,
             for example: ``AVG(column1) + 5``
@@ -543,8 +543,8 @@ def barh(
                 (ex: 50% to get the median).
             - None:
                 No Aggregations. Parameter ``of``
-                must not be empty, otherwise it
-                is ignored.
+                must be empty, otherwise it is
+                ignored.
 
             It can also be a cutomized aggregation,
             for example: ``AVG(column1) + 5``
@@ -2188,10 +2188,7 @@ def hexbin(
                 :py:class:`~vDataColumns` ``of``
                 (ex: 50% to get the median).
             - None:
-                No Aggregations. Parameter ``of``
-                must not be empty, otherwise it
-                is ignored. The function to draw
-                the final chart will be ``max```.
+                No Aggregations.
 
         of: str, optional
             The vDataColumn used to compute the aggregation.

diff --git a/verticapy/core/vdataframe/_sys.py b/verticapy/core/vdataframe/_sys.py
@@ -1328,14 +1328,14 @@ def rename(
 
         .. warning::
 
-            SQL code generation  will be slower if the
-            vDataFrame  has been transformed  multiple
-            times, so it's better practice to use this
-            method when first preparing your data.
-            It is even recommended to use directly
+            SQL code generation will be slower if the
+            ``vDataFrame`` has been transformed multiple
+            times, so it's better to use this method when
+            first preparing your data. It is even
+            recommended to use the
             ``vDataFrame.``:py:meth:`~verticapy.vDataFrame.select`
-            method and do all the renaming within
-            one single operation.
+            method directly and perform all renaming within
+            a single operation.
 
         Parameters
         ----------