From 31ccf2d4f1421c3247e9e639370dfa9d49b930d1 Mon Sep 17 00:00:00 2001
From: Alajemba <107393838+alajemba-vik@users.noreply.github.com>
Date: Tue, 7 Jan 2025 14:42:37 +0000
Subject: [PATCH] Update multiplatform-discover-project.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This PR corrects the terminology used when referring to source set naming conventions. The current text mentions “prefixes” when it should say “suffixes,” as terms like commonMain and iosArm64Main have “Main” at the end, making “suffix” the correct term.
---
 docs/topics/multiplatform/multiplatform-discover-project.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/topics/multiplatform/multiplatform-discover-project.md b/docs/topics/multiplatform/multiplatform-discover-project.md
index 7d1ca746bd8..d59a9215f2a 100644
--- a/docs/topics/multiplatform/multiplatform-discover-project.md
+++ b/docs/topics/multiplatform/multiplatform-discover-project.md
@@ -289,7 +289,7 @@ devices, respectively, you can use the `tvosMain` intermediate source set for al
 ## Integration with tests
 
 Real-life projects also require tests alongside the main production code. This is why all source sets created by
-default have the `Main` and `Test` prefixes. `Main` contains production code, while `Test` contains tests for this code.
+default have the `Main` and `Test` suffixes. `Main` contains production code, while `Test` contains tests for this code.
 The connection between them is established automatically, and tests can use the API provided by the `Main` code without
 additional configuration.