From 67d5333b1d7febb74f37f328e77ae517b2a39d3a Mon Sep 17 00:00:00 2001
From: kthui <18255193+kthui@users.noreply.github.com>
Date: Wed, 28 Jun 2023 13:37:20 -0700
Subject: [PATCH] Remove mentioning increase instance count case

---
 docs/user_guide/model_management.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/docs/user_guide/model_management.md b/docs/user_guide/model_management.md
index cfb3409ca2f..3b32358a96d 100644
--- a/docs/user_guide/model_management.md
+++ b/docs/user_guide/model_management.md
@@ -229,9 +229,6 @@ the model file), Triton does not guarentee any remaining request(s) from the
 in-flight sequence(s) will be routed to the same model instance for processing.
 It is currently the responsibility of the user to ensure any in-flight
 sequence(s) are completed before reloading a sequence model.
-  * If a sequence model is *updated* (i.e. increasing/decreasing the instance
-count), Triton will wait until the in-flight sequence is completed (or
-timed-out) before the instance behind the sequence is removed.
 
 ## Concurrently Loading Models