diff --git a/public/docs/bridgeServer.md b/public/docs/bridgeServer.md index e86bfa2..93d4340 100644 --- a/public/docs/bridgeServer.md +++ b/public/docs/bridgeServer.md @@ -6,7 +6,7 @@ Bridge Server handles bridge communication by routing messages to bridge clients The Bridge Server routes messages to bridge clients and manages bidirectional communication through phone number-based aliases. -- Gateway Server sends publishing request to Bridge Server +- Routing Server sends publishing request to Bridge Server - Bridge Server determines the target bridge for the message - Bridge Server sends message content to Vault to be decrypted - Bridge Server sends message to the appropriate bridge client diff --git a/public/docs/client.md b/public/docs/client.md index 99b7fba..acaf820 100644 --- a/public/docs/client.md +++ b/public/docs/client.md @@ -4,12 +4,12 @@ Client apps (Android/iOS) are mobile applications that allow users to publish co ##### How It Works -Client apps encrypt user messages and send them via SMS to gateway clients. OAuth2 tokens can optionally be stored locally on the device for convenience. If not stored locally, the Publisher will retrieve them from the Vault when processing platform payloads. Clients also decrypt replies to bridge messages sent via aliases. +Client apps encrypt user messages and send them via SMS to routing numbers. OAuth2 tokens can optionally be stored locally on the device for convenience. If not stored locally, the Publisher will retrieve them from the Vault when processing platform payloads. Clients also decrypt replies to bridge messages sent via aliases. - User creates message content in the mobile app - App encrypts message (with local tokens if stored) -- App sends encrypted SMS to gateway client phone number -- Gateway client receives and forwards message to system +- App sends encrypted SMS to routing numbers phone number +- Routing Numbers receives and forwards message to system - For platform payloads: Publisher retrieves tokens from Vault if not included in message - App receives SMS confirmation once content is published successfully - For bridge messages: When replies are sent to the alias, Bridge Server forwards them via SMS diff --git a/public/docs/gatewayClient.md b/public/docs/gatewayClient.md index 2f6119a..a9d5d68 100644 --- a/public/docs/gatewayClient.md +++ b/public/docs/gatewayClient.md @@ -1,15 +1,15 @@ ##### Description -Gateway clients are Android devices with internet connection that receive SMS messages from users and forward them to the Gateway Server using HTTP, SMTP, and FTP protocols. +Routing Numbers are Android devices with internet connection that receive SMS messages from users and forward them to the Routing Server using HTTP, SMTP, and FTP protocols. ##### How It Works -Gateway clients serve as intermediaries between users and the RelaySMS system, enabling SMS messages sent from users without internet access to be securely transmitted to the Gateway Server over the internet. These devices receive SMS messages and forward them using supported protocols. +Routing Numbers serve as intermediaries between users and the RelaySMS system, enabling SMS messages sent from users without internet access to be securely transmitted to the Routing Server over the internet. These devices receive SMS messages and forward them using supported protocols. -- User sends encrypted SMS message to gateway client's phone number -- Gateway client receives SMS on the Android device -- Gateway client forwards message to Gateway Server using HTTP, SMTP, or FTP protocols -- Gateway Server processes the message +- User sends encrypted SMS message to Routing Numbers phone number +- Routing Numbers receives SMS on the Android device +- Routing Numbers forwards message to Routing Server using HTTP, SMTP, or FTP protocols +- Routing Server processes the message [DekuSMS Android Repository](https://github.com/dekusms/DekuSMS-Android) @@ -17,4 +17,4 @@ Gateway clients serve as intermediaries between users and the RelaySMS system, e --- -For a complete list of available gateway clients, see the [Available Clients JSON](https://gatewayserver.smswithoutborders.com/v3/clients) +For a complete list of available Routhing Numbers, see the [Available Clients JSON](https://gatewayserver.smswithoutborders.com/v3/clients) diff --git a/public/docs/gatewayServer.md b/public/docs/gatewayServer.md index 67679fe..53c3452 100644 --- a/public/docs/gatewayServer.md +++ b/public/docs/gatewayServer.md @@ -1,15 +1,15 @@ ##### Description -Gateway Server receives SMS messages from gateway clients and routes them to the correct processing component (Publisher or Bridge Server) based on message type. The server listens on HTTP, SMTP, or FTP protocols. +Routing Server receives SMS messages from routing numbers and routes them to the correct processing component (Publisher or Bridge Server) based on message type. The server listens on HTTP, SMTP, or FTP protocols. ##### How It Works -The Gateway Server acts as the central routing hub that receives messages from gateway clients and determines where to send them for processing. +The Routing Server acts as the central routing hub that receives messages from Routing numbers and determines where to send them for processing. -- Gateway Client forwards SMS message to Gateway Server via HTTP, SMTP, or FTP -- Gateway Server receives and decodes the message to determine its type -- Gateway Server routes message to appropriate component (Publisher or Bridge Server) +- Routing Numbers forwards SMS message to Routing Server via HTTP, SMTP, or FTP +- Routing Server receives and decodes the message to determine its type +- Routing Server routes message to appropriate component (Publisher or Bridge Server) -[Gateway Server Repository](https://github.com/smswithoutborders/RelaySMS-Gateway-Server) +[Routing Server Repository](https://github.com/smswithoutborders/RelaySMS-Gateway-Server) --- diff --git a/public/docs/publisher.md b/public/docs/publisher.md index ec88c87..7207ad4 100644 --- a/public/docs/publisher.md +++ b/public/docs/publisher.md @@ -6,7 +6,7 @@ Publisher executes platform requests by retrieving tokens from the Vault and cal The Publisher acts as the execution engine that connects to various social media platforms using stored user credentials. It receives publishing requests, determines the target platform, and handles the actual API calls to deliver content. -- Gateway Server sends publishing request to Publisher +- Routing Server sends publishing request to Publisher - Publisher determines the target platform for the message - Publisher sends message content to Vault to be decrypted - Publisher requests user's tokens from Vault diff --git a/public/locales/en/translation.json b/public/locales/en/translation.json index c6ae552..6c4dd3e 100644 --- a/public/locales/en/translation.json +++ b/public/locales/en/translation.json @@ -25,7 +25,7 @@ "h1": "No Internet? No Problem. RelaySMS Keeps You Connected.", "h2": "RelaySMS enables users send messages to online platforms without an active internet connection. Messages are sent via SMS from your device.", "Android": "Download RelaySMS ", - "GatewayClient": "Set-Up Gateway Client", + "RoutingNumbers": "Set Up Gateway Clients", "supportedPlatforms": "Supported Platforms:", "auditMessage": { "part1": "RelaySMS is committed to security and transparency. Read our ", @@ -47,11 +47,11 @@ "Step3Title": "Save Platforms", "Step3Desc": "Save access to platforms while connected to the internet. Add your credentials to platforms supported by RelaySMS and prepare them for offline use.", "Step3Button": "Set Up Now", - "Step4Title": "Select a Gateway Client", - "Step4Desc": "Choose a Gateway Client for sending SMS. You can select from pre-configured clients or set up a custom client by adding the gateway number to your contacts.", - "Step4Button": "Configure Gateway", + "Step4Title": "Select a Routing Number", + "Step4Desc": "Choose a Routing Number for sending SMS. You can select from pre-configured numbers or set up a custom number by adding the routing number to your contacts.", + "Step4Button": "Configure Routing Number", "Step5Title": "Send Messages", - "Step5Desc": "Compose messages for supported platforms without internet. Send these as SMS to a pre-saved gateway number, ensuring encrypted communication.", + "Step5Desc": "Compose messages for supported platforms without internet. Send these as SMS to a pre-saved routing number, ensuring encrypted communication.", "Step5Button": "Start Messaging" }, "WhoShouldUse": { @@ -70,8 +70,8 @@ "SeeSpecification": "Read more" }, "GatewayClient": { - "Header": "Setting Up a Gateway-Client", - "Description": "Setting up a gateway client allows you and anyone you share it with to send messages using your number. It's completely optional, but if you choose to set one up, just follow the instructions below.", + "Header": "Setting Up Gateway Clients", + "Description": "Gateway Clients are devices with active internet that act as a bridge between offline users and online platforms. When you send a message without internet, it goes via SMS to a Gateway Clients which forwards it to your selected platform. Within the app, Gateway Clients are listed under the Countries tab. They can be set up using the DekuSMS app.", "ReadMore": "Read More" }, "SupportedPlatforms": { @@ -118,7 +118,7 @@ }, "faq2": { "question": "How does RelaySMS work?", - "answer": "RelaySMS works by using SMS messages sent from your app to SMS Gateway clients run by volunteers, who forward them to the internet." + "answer": "RelaySMS works by using SMS messages sent from your app to SMS Gateway Clients run by volunteers, who forward them to the internet." }, "faq3": { "question": "Do I need an internet connection to use RelaySMS?", @@ -284,7 +284,7 @@ }, "Overview": { "title": "RelaySMS System Overview", - "description": "The diagram below illustrates the flow of messages and data between the main components of the RelaySMS, from client apps through gateways, servers, and external services.", + "description": "The diagram below illustrates the flow of messages and data between the main components of the RelaySMS, from client apps through Gateway Clients, servers, and external services.", "tip": "Tip: Click on a node in the diagram to view more information about that component.", "details": "Details", "loading": "Loading documentation...", @@ -292,7 +292,7 @@ "Client": "Client", "Vault": "Vault", "Publisher": "Publisher", - "GatewayClient": "Gateway Client", + "GatewayClient": "Gateway Clients", "GatewayServer": "Gateway Server", "BridgeServer": "Bridge Server", "Platforms": "Platforms", @@ -300,7 +300,7 @@ }, "nodes": { "Client": "Client (Apps)", - "GatewayClient": "Gateway Client", + "GatewayClient": "Gateway Clients", "GatewayServer": "Gateway Server", "Publisher": "Publisher", "BridgeServer": "Bridge Server", diff --git a/src/Components/GettingStarted.js b/src/Components/GettingStarted.js index bc847a3..b180991 100644 --- a/src/Components/GettingStarted.js +++ b/src/Components/GettingStarted.js @@ -132,7 +132,7 @@ const GettingStarted = () => { title: t("Howitworks.Step4Title"), description: t("Howitworks.Step4Desc"), image: "/Gateway-copy.png", - buttonText: t("Howitworks.Step4Button", "Select a Gateway"), + buttonText: t("Howitworks.Step4Button", "Select a Routing Number"), link: "https://docs.smswithoutborders.com/docs/Android%20Tutorial/Getting-Started-With-Android#step-6-choose-a-gateway-client", bgColor: "rgb(183, 243, 232)" }, diff --git a/src/Components/Hero.js b/src/Components/Hero.js index 1b79edb..03e8a34 100644 --- a/src/Components/Hero.js +++ b/src/Components/Hero.js @@ -166,7 +166,7 @@ const Hero = () => { } }} > - {t("Landing.GatewayClient")} + {t("Landing.RoutingNumbers")} diff --git a/src/Components/WhoShouldUse.js b/src/Components/WhoShouldUse.js index 6060517..459f83c 100644 --- a/src/Components/WhoShouldUse.js +++ b/src/Components/WhoShouldUse.js @@ -184,7 +184,7 @@ const WhoShouldUse = () => { mb: 2 }} > - {t("GatewayClient.Header", "Setting Up a Gateway-Client")} + {t("GatewayClient.Header", "Setting Up Gateway Clients")} { > {t( "GatewayClient.Description", - "Setting up a gateway client allows you and anyone you share it with to send messages using your number. It's completely optional, but if you choose to set one up, just follow the instructions below." + "Gateway Clients are devices with active internet that act as a bridge between offline users and online platforms. When you send a message without internet, it goes via SMS to a Gateway Clients which forwards it to your selected platform. Within the app, Gateway Clients are listed under the Countries tab. They can be set up using the DekuSMS app." )}