Skip to content

Commit 78ffaae

Browse files
committed
docs: make description more precise
1 parent 94160e4 commit 78ffaae

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

user_guide_src/source/database/query_builder.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -506,7 +506,7 @@ You can also pass an array of multiple values as well:
506506

507507
.. literalinclude:: query_builder/049.php
508508

509-
If you are using a database that CodeIgniter escapes queries for, you
509+
If you are using a database that CodeIgniter escapes values for, you
510510
can prevent escaping content by passing an optional third argument, and
511511
setting it to ``false``.
512512

@@ -895,7 +895,7 @@ In the above example, if we assume that the ``title`` field is our primary
895895
key, then if a row containing ``My title`` as the ``title`` value, that row
896896
will be deleted with our new row data replacing it.
897897

898-
Usage of the ``set()`` method is also allowed and all fields are
898+
Usage of the ``set()`` method is also allowed and all values are
899899
automatically escaped, just like with ``insert()``.
900900

901901
$builder->set()
@@ -914,7 +914,7 @@ based on whether you are doing an insert or an update:
914914
.. literalinclude:: query_builder/084.php
915915

916916
``set()`` will also accept an optional third parameter (``$escape``), that
917-
will prevent data from being escaped if set to ``false``. To illustrate the
917+
will prevent the values from being escaped if set to ``false``. To illustrate the
918918
difference, here is ``set()`` used both with and without the escape
919919
parameter.
920920

0 commit comments

Comments
 (0)