[PATCH 2/2] Docs/mm/damon/design: replace "same to" with "same as"

From: SJ Park

Date: Mon Nov 16 2026 - 10:11:22 EST


From: Enze Li <lienze@xxxxxxxxxx>

"same to" is not idiomatic; it should be "the same as" or "same as".
This doc has six such usages. Fix all of them at once for consistency.

Signed-off-by: Enze Li <lienze@xxxxxxxxxx>
Acked-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Reviewed-by: SJ Park <sj@xxxxxxxxxx>
Signed-off-by: SJ Park <sj@xxxxxxxxxx>
---
Changes from v1
- v1: https://lore.kernel.org/20261114055436.5546-1-lienze@xxxxxxxxxx
- Collect A-b: from Randy and R-b: from SJ.
- Rebase to the latest mm-new.

Documentation/mm/damon/design.rst | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
index b676be6971589..6284b90054430 100644
--- a/Documentation/mm/damon/design.rst
+++ b/Documentation/mm/damon/design.rst
@@ -292,17 +292,17 @@ DAMON :ref:`context <damon_design_execution_model_and_data_structures>`. The
registration is made by specifying a probe per attribute. Each of the probes
specifies a rule to determine if a given memory region has the related
attribute. The rule is constructed with multiple filters. The filters work
-same to :ref:`DAMOS filters <damon_design_damos_filters>` except the supported
-filter types. Currently below filter types are supported.
+the same as :ref:`DAMOS filters <damon_design_damos_filters>` except the
+supported filter types. Currently below filter types are supported.

-- ``anon``: Same to that for DAMOS filters.
-- ``memcg``: Same to that for DAMOS filters.
+- ``anon``: Same as that for DAMOS filters.
+- ``memcg``: Same as that for DAMOS filters.
- ``pgidle_unset``: Matches if the page for the memory is marked as not
access-idle.
- ``pgidle_set``: Matches if the page for the memory is marked as access-idle.
- ``hugepage_size``: Matches if the page for the memory is a part of a hugepage
of a given size range.
-- ``active``: Same to that for DAMOS filters.
+- ``active``: Same as that for DAMOS filters.

If such probes are registered, DAMON executes the probes for each region's
sampling memory when it does the access :ref:`sampling
@@ -706,7 +706,7 @@ There are two such tuning algorithms that users can select as they need.
The goal can be specified with six parameters, namely ``target_metric``,
``complement``, ``target_value``, ``current_value``, ``nid`` and ``path``. The
auto-tuning mechanism tries to make ``current_value`` of ``complement``-ed
-``target_metric`` be same to ``target_value``.
+``target_metric`` be the same as ``target_value``.

- ``user_input``: User-provided value. Users could use any metric that they
have interest in for the value. User space main workload's latency or
@@ -736,7 +736,7 @@ auto-tuning mechanism tries to make ``current_value`` of ``complement``-ed

``complement`` is a boolean parameter that determines whether to use
complemented value of the target metric. For example, if ``complement`` is set
-and target metric is ``active_mem_bp``, it is effectively same to
+and target metric is ``active_mem_bp``, it is effectively the same as
``inactive_mem_bp``. ``complement`` is no-op when the target metric type is
``user_input``. For the metric type, the user should be able to emit
complemented metric values on their own.
--
2.47.3