From dd227d2e38c03fe1e5d2a70e49806cf26d387286 Mon Sep 17 00:00:00 2001
From: Bri <92327786+briwylde08@users.noreply.github.com>
Date: Tue, 11 Jun 2024 16:50:00 -0600
Subject: [PATCH] formatting

---
 docs/smart-contracts/tokens/wayfinding.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/smart-contracts/tokens/wayfinding.mdx b/docs/smart-contracts/tokens/wayfinding.mdx
index a3afc136d..db2f39744 100644
--- a/docs/smart-contracts/tokens/wayfinding.mdx
+++ b/docs/smart-contracts/tokens/wayfinding.mdx
@@ -50,7 +50,7 @@ Learn how to deploy a Stellar Asset Contract for an asset in [this How-To Guide]
 - Compatibility: the SAC benefits from Stellar assets' existing interoperability.
 - Cost and resource efficiency: the SAC is built into the protocol instead of being a contract that runs in a virtual machine. Each function within the SAC will be more resource-efficient than its custom-coded counterpart.
 - Less work: you don’t have to write an entirely new contract. A Stellar asset’s SAC already exists on the network and just needs to be deployed to be used.
-- Customization:  Admin addresses can be contracts. Asset issuers can set a different smart contract as an admin for their asset’s SAC. Making the admin another smart contract allows the addition of custom and decentralized logic for the assets admin capabilities, such as authorizing balances and trust lines, minting tokens, etc.
+- Customization: Admin addresses can be contracts. Asset issuers can set a different smart contract as an admin for their asset’s SAC. Making the admin another smart contract allows the addition of custom and decentralized logic for the assets admin capabilities, such as authorizing balances and trust lines, minting tokens, etc.
 
 **Downside of the SAC:**