From c44e39d9d6bfeea15c6e600c6167663c0f9196ea Mon Sep 17 00:00:00 2001
From: klotlabs <51651746+klotlabs@users.noreply.github.com>
Date: Thu, 9 Jun 2022 00:40:05 +0300
Subject: [PATCH] Update training_a_model.md (#1620)

edited `...servers our needs.` to `...serves your needs.`
---
 docs/source/training_a_model.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/source/training_a_model.md b/docs/source/training_a_model.md
index 22090f6e..989a5704 100644
--- a/docs/source/training_a_model.md
+++ b/docs/source/training_a_model.md
@@ -2,7 +2,7 @@
 
 1. Decide the model you want to use.
 
-    Each model has a different set of pros and cons that define the run-time efficiency and the voice quality. It is up to you to decide what model servers your needs. Other than referring to the papers, one easy way is to test the 🐸TTS
+    Each model has a different set of pros and cons that define the run-time efficiency and the voice quality. It is up to you to decide what model serves your needs. Other than referring to the papers, one easy way is to test the 🐸TTS
     community models and see how fast and good each of the models. Or you can start a discussion on our communication channels.
 
 2. Understand the configuration, its fields and values.
@@ -143,4 +143,4 @@ d-vectors. For using d-vectors, you first need to compute the d-vectors using th
 The same Glow-TTS model above can be trained on a multi-speaker VCTK dataset with the script below.
 
 ```{literalinclude} ../../recipes/vctk/glow_tts/train_glow_tts.py
-```
\ No newline at end of file
+```