Skip to content

Commit d2ececc

Browse files
typo [ci skip]
1 parent ff0562f commit d2ececc

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

OVERVIEW.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ handlers(list(
135135

136136
## Sticky messages
137137

138-
As seen above, some progress handlers present the progress message as part of its output, e.g. the "progress" handler will display the message as part of the progress bar. It is also possible to "push" the message up together with other terminal output. This can be done by add class attribute `"sticky"` to the progression signaled. This works for several progress handlers that output to the terminal. For example, with:
138+
As seen above, some progress handlers present the progress message as part of its output, e.g. the "progress" handler will display the message as part of the progress bar. It is also possible to "push" the message up together with other terminal output. This can be done by adding class attribute `"sticky"` to the progression signaled. This works for several progress handlers that output to the terminal. For example, with:
139139

140140
```r
141141
slow_sum <- function(x) {

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ handlers(list(
137137

138138
## Sticky messages
139139

140-
As seen above, some progress handlers present the progress message as part of its output, e.g. the "progress" handler will display the message as part of the progress bar. It is also possible to "push" the message up together with other terminal output. This can be done by add class attribute `"sticky"` to the progression signaled. This works for several progress handlers that output to the terminal. For example, with:
140+
As seen above, some progress handlers present the progress message as part of its output, e.g. the "progress" handler will display the message as part of the progress bar. It is also possible to "push" the message up together with other terminal output. This can be done by adding class attribute `"sticky"` to the progression signaled. This works for several progress handlers that output to the terminal. For example, with:
141141

142142
```r
143143
slow_sum <- function(x) {

vignettes/progressr-intro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ handlers(list(
144144

145145
## Sticky messages
146146

147-
As seen above, some progress handlers present the progress message as part of its output, e.g. the "progress" handler will display the message as part of the progress bar. It is also possible to "push" the message up together with other terminal output. This can be done by add class attribute `"sticky"` to the progression signaled. This works for several progress handlers that output to the terminal. For example, with:
147+
As seen above, some progress handlers present the progress message as part of its output, e.g. the "progress" handler will display the message as part of the progress bar. It is also possible to "push" the message up together with other terminal output. This can be done by adding class attribute `"sticky"` to the progression signaled. This works for several progress handlers that output to the terminal. For example, with:
148148

149149
```r
150150
slow_sum <- function(x) {

0 commit comments

Comments
 (0)