Skip to content

Commit 341d074

Browse files
committed
Remove instances of "the the"
1 parent a7cf9a8 commit 341d074

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/install-create-run.qmd

+1-1
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ If you still find that too obtrusive and aren't used to working with type hints,
122122

123123
In the above configuration, we also disable the `reportUnusedFunction` diagnostic, as it's idiomatic Shiny to create named functions that are never explicitly called by any code (i.e., `@reactive.effect`).
124124

125-
You can also modify these settings on a per-file basis with comments at the top of the file. For example, you might have something like this at the the top of your `app.py`:
125+
You can also modify these settings on a per-file basis with comments at the top of the file. For example, you might have something like this at the top of your `app.py`:
126126

127127
```default
128128
# pyright: strict

docs/reactive-mutable.qmd

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ b
3636

3737
If our goal is to end up with `a == [1, 2, 3]` and `b == [1, 2]`, then we've failed.
3838

39-
Mutability can cause unexpected behavior in any Python program, but especially so in reactive programming. For example, if you modify a mutable object stored in a ` reactive.value`, or one returned from a `reactive.calc`, other consumers of those values will have their values changed. This can cause two different problems. First, the altered value will probably be unexpected. Second, even if the the change in value is expected and desired, it will not trigger downstream reactive objects to re-execute.
39+
Mutability can cause unexpected behavior in any Python program, but especially so in reactive programming. For example, if you modify a mutable object stored in a ` reactive.value`, or one returned from a `reactive.calc`, other consumers of those values will have their values changed. This can cause two different problems. First, the altered value will probably be unexpected. Second, even if the change in value is expected and desired, it will not trigger downstream reactive objects to re-execute.
4040

4141

4242
## Solutions

0 commit comments

Comments
 (0)