From a508b264eda4bc3c99ba1f44eab1dec6e5ce06c0 Mon Sep 17 00:00:00 2001
From: Jay Kwak <82421531+jkwak-work@users.noreply.github.com>
Date: Fri, 25 Oct 2024 21:12:37 -0700
Subject: Swap the term StdLib with Core-Module or Standard-Module in documents
 (#5414)

This PR is limited to documents.
All use of "Standard library" or "StdLib" are replaced with either "core module" or "standard modules", depending on the context.
---
 docs/design/coding-conventions.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/design/coding-conventions.md')

diff --git a/docs/design/coding-conventions.md b/docs/design/coding-conventions.md
index b2492685f..228b26de7 100644
--- a/docs/design/coding-conventions.md
+++ b/docs/design/coding-conventions.md
@@ -72,7 +72,7 @@ As a general rule, default to making the implementation of a type `public`, and
 
 ### Slang
 
-The Slang project codebase also includes `.slang` files implementing the Slang standard library, as well as various test cases and examples.
+The Slang project codebase also includes `.slang` files implementing the Slang core module, as well as various test cases and examples.
 The conventions described here are thus the "official" recommendations for how users should format Slang code.
 
 To the extent possible, we will try to apply the same basic conventions to both C++ and Slang.
@@ -132,7 +132,7 @@ Namespaces
 Favor fewer namespaces when possible.
 Small programs may not need any.
 
-All library code that a Slang user might link against should go in the `Slang` namespace for now, to avoid any possibility of clashes in a static linking scenario.
+All standard module code that a Slang user might link against should go in the `Slang` namespace for now, to avoid any possibility of clashes in a static linking scenario.
 The public C API is obviously an exception to this.
 
 
-- 
cgit v1.2.3