From 54ec3046c47958c6de072be599efb88f49eec4e4 Mon Sep 17 00:00:00 2001
From: Adarsh Santoria <108261986+AdarshSantoria@users.noreply.github.com>
Date: Wed, 1 Feb 2023 17:02:45 +0530
Subject: [PATCH] fixing typo in trees.md

---
 doc/developer/trees.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/developer/trees.md b/doc/developer/trees.md
index 6321e1ebe8..19e6c490e4 100644
--- a/doc/developer/trees.md
+++ b/doc/developer/trees.md
@@ -86,7 +86,7 @@ restatement of the fourth part of the definition).
 
 Most everything in mlpack is decomposed into a series of configurable template
 parameters, and trees are no exception.  In order to ease usage of high-level
-mlpack algorithms, each \c TreeType itself must be a template class taking three
+mlpack algorithms, each TreeType itself must be a template class taking three
 parameters:
 
  - `MetricType` -- the underlying metric that the tree will be built on (see
@@ -424,7 +424,7 @@ This constructor should be called with `(*this)` after the node is constructed
 The last template parameter is the `MatType` parameter.  This is generally
 `arma::mat` or `arma::sp_mat`, but could be any Armadillo type, including
 matrices that hold data points of different precisions (such as `float` or even
-`int`).  It generally suffices to write \c MatType assuming that `arma::mat`
+`int`).  It generally suffices to write MatType assuming that `arma::mat`
 will be used, since the vast majority of the time this will be what is used.
 
 ### Constructors and destructors