From 2094406df9c4a029f62048554d8e37aa009ad09b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micka=C3=ABl=20Canouil?=
 <8896044+mcanouil@users.noreply.github.com>
Date: Fri, 18 Oct 2024 11:44:48 +0200
Subject: [PATCH] fix: typos in "hier_clust.Rmd"

---
 vignettes/articles/hier_clust.Rmd | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/vignettes/articles/hier_clust.Rmd b/vignettes/articles/hier_clust.Rmd
index 063213d1..d2aa59e3 100644
--- a/vignettes/articles/hier_clust.Rmd
+++ b/vignettes/articles/hier_clust.Rmd
@@ -107,7 +107,7 @@ fake_dat %>%
 ```
 
 This process continues, with the closest two clusters being joined (or 
-"aggolermated") at each step.
+"agglomerated") at each step.
 
 
 ```{r, echo = FALSE}
@@ -198,7 +198,7 @@ tibble(
 ```
 
 
-### Methods of aggolmeration
+### Methods of agglomeration
 
 At every step of the agglomeration, we measure distances between current
 clusters.  With each cluster containing (possibly) multiple points, what does
@@ -331,7 +331,7 @@ hc_preds
 
 It's important to note that there is no guarantee that `predict()` on the 
 training data will produce the same results as `extract_cluster_assignments()`.
-The process by which clusters are created during the aggolmerations results in
+The process by which clusters are created during the agglomerations results in
 a particular partition; but if a training observation is treated as new data, it
 is predicted in the same manner as truly new information.