stellar · briwylde08 · Apr 7, 2026 · Oct 25, 2023 · Jun 15, 2024 · Dec 18, 2025
diff --git a/docs/build/apps/wallet/sep24.mdx b/docs/build/apps/wallet/sep24.mdx
@@ -712,7 +712,7 @@ onMessage: (transaction) => {
     // Signs it with the account key pair
     transferTransaction.sign(keypair);
 
-    // Finally submits it to the stellar network. This stellar.submitTransaction()
+    // Finally submits it to the Stellar network. This stellar.submitTransaction()
     // function handles '504' status codes (timeout) by keep retrying it until
     // submission succeeds or we get a different error.
     try {
@@ -743,7 +743,7 @@ onMessage: (transaction) => {
           type: 'https://stellar.org/horizon-errors/transaction_failed',
           title: 'Transaction Failed',
           status: 400,
-          detail: 'The transaction failed when submitted to the stellar network.
+          detail: 'The transaction failed when submitted to the Stellar network.
             The `extras.result_codes` field on this response contains further details.
             Descriptions of each code can be found at:
             https://developers.stellar.org/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed',

diff --git a/docs/data/apis/horizon/admin-guide/monitoring.mdx b/docs/data/apis/horizon/admin-guide/monitoring.mdx
@@ -23,8 +23,8 @@ There are numerous application metrics keys emitted by Horizon at runtime, encod
 
 - `go_`: golang specfic runtime performance
 - `horizon_txsub_`: attributes of Horizon transaction submission sub system if enabled.
-- `horizon_stellar_core_`: runtime attributes of stellar network reported by the captive core.
-- `horizon_order_book_`: runtime attributes of the in memory order book maintained by Horizon of the current stellar network
+- `horizon_stellar_core_`: runtime attributes of Stellar network reported by the captive core.
+- `horizon_order_book_`: runtime attributes of the in memory order book maintained by Horizon of the current Stellar network
 - `horizon_log_`: counters of how many log messages printed at each severity level
 - `horizon_ingest_`: performance measurements and stateful aspects of Horizon's internal ingestion sub system
 - `horizon_http_`: statistics and measurements of Horizon's HTTP API service, all aspects of request/response load and timings.

diff --git a/...izon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx b/...izon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
@@ -14,7 +14,7 @@ The `before_history` error returns a [`410` error code](https://developer.mozill
   "type": "https://stellar.org/horizon-errors/before_history",
   "title": "Data Requested Is Before Recorded History",
   "status": 410,
-  "detail": "This horizon instance is configured to only track a portion of the stellar network's latest history. This request is asking for results prior to the recorded history known to this horizon instance."
+  "detail": "This horizon instance is configured to only track a portion of the Stellar network's latest history. This request is asking for results prior to the recorded history known to this horizon instance."
 }
 ```
 

diff --git a/.../api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx b/.../api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx
@@ -20,7 +20,7 @@ In almost every case, this error indicates that the transaction submitted in the
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
   "status": 400,
-  "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/guides/concepts/list-of-operations.html",
+  "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/guides/concepts/list-of-operations.html",
   "extras": {
     "envelope_xdr": "AAAAAgAAAADdfhHDs4Vaug6p8Oxb1QRjNRdJt3pYKKBVhFHrEgd9QAAAAAoAEi4YAAAAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACwAAAAAAAAAAAAAAAAAAAAESB31AAAAAQFhc/liVXbLk3NtB2BtweFJ064JdDIfrTSrqKMhb1oIRK+0PSyvjzZTkRCJmQY3bHNXYNuepa2TF7aBdibrb1gI=",
     "result_codes": {

diff --git a/docs/data/apis/horizon/api-reference/errors/response.mdx b/docs/data/apis/horizon/api-reference/errors/response.mdx
@@ -47,7 +47,7 @@ When any error occurs, Horizon responds with a JSON document with the below attr
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
   "status": 400,
-  "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
+  "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
   "extras": {
     "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==",
     "result_codes": {

diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx
@@ -38,7 +38,7 @@ These are Result Codes that communicate success (200) or failure (400) at the op
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
   "status": 400,
-  "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
+  "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
   "extras": {
     "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==",
     "result_codes": {

diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx
@@ -56,7 +56,7 @@ These are Result Codes that communicate success (200) or failure (400) at the tr
   "type": "https://stellar.org/horizon-errors/transaction_failed",
   "title": "Transaction Failed",
   "status": 400,
-  "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
+  "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details.  Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
   "extras": {
     "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAArki/TnIipBc7Y+Hd87mnZdtBxzm7vu6iXpwcRz6zGskAAAAAAAAAAAAHoSAAAAAAAAAAAdJBKRwAAABANWeKuRYFmBm1lrMQqMvhbSouwL270SnxcTtv1XI4Y+uVe4yw4Jq7/43EoxwLbRh/pC3V4WfOZRzDqwsTyEztAA==",
     "result_codes": {

diff --git a/docs/data/indexers/build-your-own/ingest-sdk/README.mdx b/docs/data/indexers/build-your-own/ingest-sdk/README.mdx
@@ -20,7 +20,7 @@ Obtain the final state of [ledger entries](../../../../learn/fundamentals/stella
 Ledger entries are cryptographically signed as part of each ledger and therefore represent the trusted, cumulative state at a point in time for [assets](../../../../learn/fundamentals/stellar-data-structures/assets.mdx) related to an [account](../../../../learn/fundamentals/stellar-data-structures/accounts.mdx) or [contract](../../../../learn/fundamentals/contract-development/storage/persisting-data.mdx). Examples of asset types:
 
 - trustlines which hold token balances
-- offers which hold bid and asks on the [stellar network DEX](../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#sdex)
+- offers which hold bid and asks on the [Stellar DEX](../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#sdex)
 - contract data which holds key/value stores for contracts
 
 ### Ledger Metadata

diff --git a/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json b/docs/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
@@ -27,7 +27,7 @@
     {
       "name": "do_stellar_payment",
       "summary": "Submits a Stellar payment",
-      "description": "Submits a payment to a stellar network by a custody service.",
+      "description": "Submits a payment to the Stellar network by a custody service.",
       "paramStructure": "by-name",
       "tags": [
         {
@@ -386,7 +386,7 @@
     {
       "name": "do_stellar_refund",
       "summary": "Submits a Stellar refund",
-      "description": "Submits a refund payment to a stellar network by a custody service",
+      "description": "Submits a refund payment to the Stellar network by a custody service",
       "paramStructure": "by-name",
       "tags": [
         {

diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/example.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/example.mdx
@@ -138,7 +138,7 @@ const sessions = {};
  * Create an authenticated session for the user.
  *
  * Return a session token to be used in future requests as well as the
- * user data. Note that you may not have a user for the stellar account
+ * user data. Note that you may not have a user for the Stellar account
  * provided, in which case the user should go through your onboarding
  * process.
  */

diff --git a/docs/tools/cli/cookbook/stellar-keys.mdx b/docs/tools/cli/cookbook/stellar-keys.mdx
@@ -1,7 +1,7 @@
 ---
 title: Stellar Keys
 hide_table_of_contents: true
-description: Manage stellar keys
+description: Manage Stellar keys
 ---
 
 Stub file: the real file is generated in build time by `yarn stellar-cli:build`.
diff --git a/docs/tools/ramps/moneygram.mdx b/docs/tools/ramps/moneygram.mdx
@@ -6,4 +6,4 @@ sidebar_position: 10
 
 MoneyGram Ramps is a MoneyGram product that enables users of third-party applications, such as crypto wallets and exchanges, to cash-in (deposit) and cash-out (withdrawal) USDC on Stellar.
 
-[Dive into the MoneyGram Ramps docs](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps) to learn about the technical requirements for integrating MoneyGram Ramps into an existing wallet or creating a new wallet application.
+Dive into the [MoneyGram Ramps docs](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps) to learn about the technical requirements for integrating MoneyGram Ramps into an existing wallet or creating a new wallet application.
diff --git a/docs/validators/admin-guide/installation.mdx b/docs/validators/admin-guide/installation.mdx
@@ -53,7 +53,7 @@ We publish multiple packages for convenience.
 | stellar-core | none | installs stellar-core binary, systemd service, logrotate script, documentation |
 | stellar-core-utils | none | installs useful command line tools (stellar-core-cmd, stellar-core-gap-detect) |
 | stellar-core-prometheus-exporter | none | installs a Prometheus exporter to facilitate ingesting stellar-core metrics |
-| stellar-core-postgres | stellar-core, PostgreSQL | configures a PostgreSQL server, creates a stellar db,role and system user, the default stellar-core configuration contained in this package will connect to the Testnet |
+| stellar-core-postgres | stellar-core, PostgreSQL | configures a PostgreSQL server, creates a Stellar DB,role and system user, the default stellar-core configuration contained in this package will connect to the Testnet |
 | stellar-archivist | none | installs stellar-archivist cli tool for managing stellar-core History archives |
 
 To install a chosen package run:

diff --git a/docs/validators/admin-guide/publishing-history-archives.mdx b/docs/validators/admin-guide/publishing-history-archives.mdx
@@ -282,7 +282,7 @@ stellar-archivist scan file:///mnt/xvdf/stellar-core-archive/node_001
 2019/04/25 12:15:41 No missing buckets referenced in range [0x0000003f, 0x000041bf]
 ```
 
-Finally, you can start your stellar Core instance once again.
+Finally, you can start your Stellar Core instance once again.
 
 ```bash
 systemctl start stellar-core

diff --git a/openrpc/src/anchor-platform/methods/do_stellar_payment.json b/openrpc/src/anchor-platform/methods/do_stellar_payment.json
@@ -1,7 +1,7 @@
 {
   "name": "do_stellar_payment",
   "summary": "Submits a Stellar payment",
-  "description": "Submits a payment to a stellar network by a custody service.",
+  "description": "Submits a payment to the Stellar network by a custody service.",
   "paramStructure": "by-name",
   "tags": [
     { "name": "SEP-6" },

diff --git a/openrpc/src/anchor-platform/methods/do_stellar_refund.json b/openrpc/src/anchor-platform/methods/do_stellar_refund.json
@@ -1,7 +1,7 @@
 {
   "name": "do_stellar_refund",
   "summary": "Submits a Stellar refund",
-  "description": "Submits a refund payment to a stellar network by a custody service",
+  "description": "Submits a refund payment to the Stellar network by a custody service",
   "paramStructure": "by-name",
   "tags": [
     { "name": "SEP-6" },

diff --git a/scripts/stellar_cli.mjs b/scripts/stellar_cli.mjs
@@ -49,7 +49,7 @@ const fullHelpDocsContent = fs.readFileSync(fullHelpDocsPath, "utf8");
 
 const modifiedContent = `---
 sidebar_position: 10
-description: This document contains the help content for the stellar command-line program.
+description: This document contains the help content for the Stellar command-line program.
 ---
 
 ${fullHelpDocsContent}
Original file line number	Diff line number	Diff line change
Expand Up		@@ -6,4 +6,4 @@ sidebar_position: 10

		MoneyGram Ramps is a MoneyGram product that enables users of third-party applications, such as crypto wallets and exchanges, to cash-in (deposit) and cash-out (withdrawal) USDC on Stellar.

		[Dive into the MoneyGram Ramps docs](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps) to learn about the technical requirements for integrating MoneyGram Ramps into an existing wallet or creating a new wallet application.
		Dive into the [MoneyGram Ramps docs](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps) to learn about the technical requirements for integrating MoneyGram Ramps into an existing wallet or creating a new wallet application.
Comment thread JFWooten4 marked this conversation as resolved.