Skip to content

Commit 96af4dd

Browse files
committed
rebuild readme
1 parent deba949 commit 96af4dd

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

README.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -79,19 +79,19 @@ between implementations.
7979

8080
In this example:
8181

82-
- the **type** of model is “random forest”,
83-
- the **mode** of the model is “regression” (as opposed to
82+
- the **type** of model is “random forest”,
83+
- the **mode** of the model is “regression” (as opposed to
8484
classification, etc), and
85-
- the computational **engine** is the name of the R package.
85+
- the computational **engine** is the name of the R package.
8686

8787
The goals of parsnip are to:
8888

89-
- Separate the definition of a model from its evaluation.
90-
- Decouple the model specification from the implementation (whether
89+
- Separate the definition of a model from its evaluation.
90+
- Decouple the model specification from the implementation (whether
9191
the implementation is in R, spark, or something else). For example,
9292
the user would call `rand_forest` instead of `ranger::ranger` or
9393
other specific packages.
94-
- Harmonize argument names (e.g. `n.trees`, `ntrees`, `trees`) so that
94+
- Harmonize argument names (e.g. `n.trees`, `ntrees`, `trees`) so that
9595
users only need to remember a single name. This will help *across*
9696
model types too so that `trees` will be the same argument across
9797
random forest as well as boosting or bagging.
@@ -142,7 +142,7 @@ rand_forest(mtry = 10, trees = 2000) %>%
142142
fit(mpg ~ ., data = mtcars)
143143
#> parsnip model object
144144
#>
145-
#> Fit time: 71ms
145+
#> Fit time: 73ms
146146
#> Ranger result
147147
#>
148148
#> Call:
@@ -172,18 +172,18 @@ This project is released with a [Contributor Code of
172172
Conduct](https://contributor-covenant.org/version/2/0/CODE_OF_CONDUCT.html).
173173
By contributing to this project, you agree to abide by its terms.
174174

175-
- For questions and discussions about tidymodels packages, modeling,
175+
- For questions and discussions about tidymodels packages, modeling,
176176
and machine learning, please [post on RStudio
177177
Community](https://community.rstudio.com/new-topic?category_id=15&tags=tidymodels,question).
178178

179-
- If you think you have encountered a bug, please [submit an
179+
- If you think you have encountered a bug, please [submit an
180180
issue](https://github.com/tidymodels/parsnip/issues).
181181

182-
- Either way, learn how to create and share a
182+
- Either way, learn how to create and share a
183183
[reprex](https://reprex.tidyverse.org/articles/articles/learn-reprex.html)
184184
(a minimal, reproducible example), to clearly communicate about your
185185
code.
186186

187-
- Check out further details on [contributing guidelines for tidymodels
187+
- Check out further details on [contributing guidelines for tidymodels
188188
packages](https://www.tidymodels.org/contribute/) and [how to get
189189
help](https://www.tidymodels.org/help/).

0 commit comments

Comments
 (0)