From 08683ae2184899b42c362335afbe62b6aeec86c7 Mon Sep 17 00:00:00 2001 From: mattijn Date: Fri, 7 Oct 2022 21:28:03 +0200 Subject: [PATCH] omission during rebase --- doc/user_guide/interactions.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/user_guide/interactions.rst b/doc/user_guide/interactions.rst index c768aed24..80b75b760 100644 --- a/doc/user_guide/interactions.rst +++ b/doc/user_guide/interactions.rst @@ -81,7 +81,7 @@ In order to use this variable in the chart specification, we explicitly add it t op_var ) -It's reasonable to ask whether all this effort is necessary. Here is a more natural way to accomplish the same thing. We avoid the use of both :func:`alt.param` and ``add_param``. +It's reasonable to ask whether all this effort is necessary. Here is a more natural way to accomplish the same thing. We avoid the use of both :func:`alt.param` and ``add_params``. .. altair-plot:: @@ -182,7 +182,7 @@ a selection region, and to move this region once the region is created. So far this example is very similar to what we did in the :ref:`variable example `: we created a selection parameter using ``brush = alt.selection_interval()``, -and we attached that parameter to the chart using ``add_param``. +and we attached that parameter to the chart using ``add_params``. Conditions: Making the Chart Respond ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~