Skip to content

Commit 1f8b2c8

Browse files
committed
fix: correct syntax
fixes #33
1 parent 837dfee commit 1f8b2c8

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

altair_introduction.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1034,7 +1034,7 @@
10341034
"id": "-HeJcwblnl10"
10351035
},
10361036
"source": [
1037-
"The two styles of specifying encodings can be interleaved: `x='precip', alt.Y('city')` is also a valid input to the `encode` function.\n",
1037+
"The two styles of specifying encodings can be interleaved: `x='precip', y=alt.Y('city')` is also a valid input to the `encode` function.\n",
10381038
"\n",
10391039
"In the examples above, the data type for each field is inferred automatically based on its type within the Pandas data frame. We can also explicitly indicate the data type to Altair by annotating the field name:\n",
10401040
"\n",

marimo/01_introduction.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -249,7 +249,7 @@ def _(alt, df):
249249
@app.cell(hide_code=True)
250250
def _(mo):
251251
mo.md(r"""
252-
The two styles of specifying encodings can be interleaved: `x='precip', alt.Y('city')` is also a valid input to the `encode` function.
252+
The two styles of specifying encodings can be interleaved: `x='precip', y=alt.Y('city')` is also a valid input to the `encode` function.
253253
254254
In the examples above, the data type for each field is inferred automatically based on its type within the Pandas data frame. We can also explicitly indicate the data type to Altair by annotating the field name:
255255

0 commit comments

Comments
 (0)