From e9f0b0ac3ea839c7270b1ce6f7728a519032890b Mon Sep 17 00:00:00 2001
From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com>
Date: Mon, 19 Jul 2021 10:43:12 -0700
Subject: [PATCH] Update selection.md

---
 docs/core/versions/selection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/core/versions/selection.md b/docs/core/versions/selection.md
index fd13ae7a54a04..4fce9dacd11ce 100644
--- a/docs/core/versions/selection.md
+++ b/docs/core/versions/selection.md
@@ -93,7 +93,7 @@ A few usage examples demonstrate the behavior, if you target 5.0:
 Minor version roll-forward has one side-effect that may affect end users. Consider the following scenario:
 
 01. The application specifies that 5.0 is required.
-02. When run, version 5.0.* isn't installed, however, 5.1.0 is. Version 3.1.0 will be used.
+02. When run, version 5.0.* isn't installed, however, 5.1.0 is. Version 5.1.0 will be used.
 03. Later, the user installs 5.0.3 and runs the application again, 5.0.3 will now be used.
 
 It's possible that 5.0.3 and 5.1.0 behave differently, particularly for scenarios like serializing binary data.