docs: capitalize segments' names

.llms-snapshots/llms.txt

@@ -91,7 +91,7 @@ Juno is your self-contained serverless platform for building full-stack web apps
 
 ## Guides
 
-- [AI](https://juno.build/docs/guides/ai.md): Learn how to use Juno's llms.txt files to provide AI tools with better context for building serverless functions, deploying satellites, and integrating the SDK.
+- [AI](https://juno.build/docs/guides/ai.md): Learn how to use Juno's llms.txt files to provide AI tools with better context for building serverless functions, deploying Satellites, and integrating the SDK.
 - [Angular](https://juno.build/docs/guides/angular.md): Explore how to create a Juno project developed with Angular.
 - [Astro](https://juno.build/docs/guides/astro.md): Explore how to create a Juno project developed with Astro.
 - [Docusaurus](https://juno.build/docs/guides/docusaurus.md): Explore how to deploy a Juno project developed with Docusaurus.
@@ -108,16 +108,16 @@ Juno is your self-contained serverless platform for building full-stack web apps
 ## Guides - Angular
 
 - [Build an Angular App](https://juno.build/docs/guides/angular/build.md): Learn how to integrate Juno with Angular. Follow our quickstart guide to set up your development environment, configure your project, and start building with Juno.
-- [Deploy an Angular App](https://juno.build/docs/guides/angular/deploy.md): Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.
+- [Deploy an Angular App](https://juno.build/docs/guides/angular/deploy.md): Learn how to deploy your Angular project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.
 
 ## Guides - Astro
 
 - [Build an Astro App](https://juno.build/docs/guides/astro/build.md): Learn how to integrate Juno with Astro. Follow our quickstart guide to set up your development environment, configure your project, and start building with Juno.
-- [Deploy an Astro Site](https://juno.build/docs/guides/astro/deploy.md): Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.
+- [Deploy an Astro Site](https://juno.build/docs/guides/astro/deploy.md): Learn how to deploy your Astro project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.
 
 ## Guides - Docusaurus
 
-- [Deploy a Docusaurus Site](https://juno.build/docs/guides/docusaurus/deploy.md): Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.
+- [Deploy a Docusaurus Site](https://juno.build/docs/guides/docusaurus/deploy.md): Learn how to deploy your Docusaurus project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.
 
 ## Guides - Github-actions
 
@@ -133,7 +133,7 @@ Juno is your self-contained serverless platform for building full-stack web apps
 ## Guides - React
 
 - [Build a React App](https://juno.build/docs/guides/react/build.md): Learn how to integrate Juno with React. Follow our quickstart guide to set up your development environment, configure your project, and start building with Juno.
-- [Deploy a React App](https://juno.build/docs/guides/react/deploy.md): Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your satellite, and publish your site to production.
+- [Deploy a React App](https://juno.build/docs/guides/react/deploy.md): Learn how to deploy your React project to Juno. Follow the deployment guide to configure static exports, set up your Satellite, and publish your site to production.
 
 ## Guides - Sveltekit
 

docs/build/analytics/index.md

@@ -69,7 +69,7 @@ All tracked data is securely stored on the [Internet Computer](https://internetc
 
 ### No cross-dapp tracking
 
-Juno Analytics does not follow users across websites and applications they visit. All data remains isolated to a single satellite.
+Juno Analytics does not follow users across websites and applications they visit. All data remains isolated to a single Satellite.
 
 ### You 100% own your data
 
@@ -83,7 +83,7 @@ You have the capability to delete all collected data within your Analytics at an
 
 To gather analytics for your dapps, you need to create an [orbiter]. Creating an Orbiter requires ICP, and its price is defined in the [transaction costs](../../pricing#transaction-costs).
 
-Each orbiter is used to collect analytics for one or multiple [satellites].
+Each Orbiter is used to collect analytics for one or multiple [satellites].
 
 Page views are collected anonymously and saved with a unique random ID for attribution. This data is organized based on its collection timestamp.
 
@@ -95,11 +95,11 @@ Additionally, a unique random session ID is generated for all data. Each time a
 
 ## Limitation
 
-Currently, an orbiter can store up to 500 GB of data.
+Currently, an Orbiter can store up to 500 GB of data.
 
 :::caution
 
-Similar to other analytics services, an Orbiter accepts data submitted from any source as long as the requested payload matches the expected format, and the targeted satellite is configured to accept analytics. This is because the origin of the HTTP request cannot be accessed, for a valid reason – to prevent tracking. Therefore, calls cannot be limited to the domain of your dapps.
+Similar to other analytics services, an Orbiter accepts data submitted from any source as long as the requested payload matches the expected format, and the targeted Satellite is configured to accept analytics. This is because the origin of the HTTP request cannot be accessed, for a valid reason – to prevent tracking. Therefore, calls cannot be limited to the domain of your dapps.
 
 Consequently, this leaves the canister open to potential attacks that can pollute the data and consume cycles. For this reason, we recommend the following:
 

docs/build/authentication/internet-identity.md

@@ -7,7 +7,7 @@ keywords: [Internet Identity, decentralized authentication, Internet Computer]
 
 [Internet Identity](https://identity.ic0.app) lets users authenticate securely and anonymously through a decentralized identity system built for the Internet Computer.
 
-When a user signs in with Internet Identity, they confirm their identity through the provider. If successful, a session is created automatically and the user can interact with your satellite.
+When a user signs in with Internet Identity, they confirm their identity through the provider. If successful, a session is created automatically and the user can interact with your Satellite.
 
 Authentication with Internet Identity offers strong privacy guarantees and complete isolation between domains by design.
 
@@ -46,7 +46,7 @@ Internet Identity sign-in can be customized with options that let you control se
 | ---------------------------- | ---------------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `maxTimeToLiveInNanoseconds` | `BigInt(4 * 60 * 60 * 1000 * 1000 * 1000)`     | **4 hours**            | Maximum lifetime of the user's session in **nanoseconds**. Once expired, the session cannot be extended.                                                                                                                                                            |
 | `windowed`                   | `boolean`                                      | `true`                 | By default, the authentication flow is presented in a popup window on desktop that is automatically centered on the browser. This behavior can be turned off by setting the option to `false`, causing the authentication flow to happen in a separate tab instead. |
-| `derivationOrigin`           | `string` or `URL`                              |                        | The main domain to be used to ensure your users are identified with the same public ID, regardless of which of your satellite's URLs they use to access your application.                                                                                           |
+| `derivationOrigin`           | `string` or `URL`                              |                        | The main domain to be used to ensure your users are identified with the same public ID, regardless of which of your Satellite's URLs they use to access your application.                                                                                           |
 | `onProgress`                 | `(progress) => void`                           |                        | Callback for provider sign-in and user creation/loading.                                                                                                                                                                                                            |
 | `domain`                     | `internetcomputer.org` or `ic0.app` or `id.ai` | `internetcomputer.org` | The domain on which to open Internet Identity.                                                                                                                                                                                                                      |
 
@@ -141,6 +141,6 @@ If you're unsure which domain to use as the primary domain, here are two common
 - Alternatively, stick with **the default domain** (`{satellite-id}.icp0.io`) if:
   - You're still experimenting with your domain setup and might change it later.
   - You're not ready to commit to a long-term domain.
-  - You plan to host multiple satellites under different domains and don't want to tie user identity to just one.
+  - You plan to host multiple Satellites under different domains and don't want to tie user identity to just one.
 
 Choosing the right derivation origin early helps avoid identity issues later, but both approaches are valid depending on your goals.

docs/build/components/encoding.mdx

@@ -1,4 +1,4 @@
-When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the satellite to provide the appropriate HTTP response header `Content-Encoding`.
+When deploying, the CLI automatically maps the encoding type based on the file extension. The encoding information is then used in the Satellite to provide the appropriate HTTP response header `Content-Encoding`.
 
 The default mappings are as follows:
 

docs/build/components/http-headers.mdx

@@ -1,4 +1,4 @@
-Headers allow the client and the satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content.
+Headers allow the client and the Satellite to pass additional information along with a request or a response. Some sets of headers can affect how the browser handles the page and its content.
 
 For instance, you may want to set a specific `Cache-Control` for performance reasons.
 

docs/build/components/ignore-files.mdx

@@ -1,4 +1,4 @@
-The `ignore` attribute allows you to exclude certain files from being deployed to your satellite.
+The `ignore` attribute allows you to exclude certain files from being deployed to your Satellite.
 
 This attribute works similarly to Git's `.gitignore`, and you can specify which files to ignore using globs.
 

docs/build/components/source.mdx

@@ -1,10 +1,10 @@
-The `source` field specifies the directory that contains the built assets for your satellite. This is typically the output directory generated by your build process after running a command like `npm run build`.
+The `source` field specifies the directory that contains the built assets for your Satellite. This is typically the output directory generated by your build process after running a command like `npm run build`.
 
 import Examples from "./source-examples.mdx";
 
 <Examples />
 
-Juno uses this directory to locate the files that will be deployed as part of your satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires.
+Juno uses this directory to locate the files that will be deployed as part of your Satellite. Ensure that this directory includes all the necessary assets, such as HTML, JavaScript, CSS, and any other static or dynamic resources your application requires.
 
 ```javascript title="juno.config.js"
 import { defineConfig } from "@junobuild/config";

docs/build/datastore/collections.md

@@ -28,9 +28,9 @@ Permissions define who can read and write documents in a collection. Writing inc
 | Permission     | Description                                                                                                                                                                                                                                 |
 | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Public**     | Anyone can read or write documents in the collection.                                                                                                                                                                                       |
-| **Private**    | Only the creator (owner) of a document can read or write to it. However, note that since satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. |
-| **Managed**    | The owner of a document, the administrator and editor of the satellite can read or write to it in the collection.                                                                                                                           |
-| **Restricted** | Only satellite administrator and editor can read or write any document in the collection.                                                                                                                                                   |
+| **Private**    | Only the creator (owner) of a document can read or write to it. However, note that since Satellite administrators manage the underlying infrastructure, they have the technical ability to modify access rules by changing its source code. |
+| **Managed**    | The owner of a document, the administrator and editor of the Satellite can read or write to it in the collection.                                                                                                                           |
+| **Restricted** | Only Satellite administrator and editor can read or write any document in the collection.                                                                                                                                                   |
 
 If not set to immutable, you can modify the permissions at any time, and the changes will take effect immediately.
 

docs/build/datastore/development.mdx

@@ -129,7 +129,7 @@ await setDoc({
 });
 ```
 
-The `version` must match the current version of the last document within the satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is useful, for example, if your users use your projects simultaneously on multiple devices.
+The `version` must match the current version of the last document within the Satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is useful, for example, if your users use your projects simultaneously on multiple devices.
 
 :::tip
 
@@ -387,7 +387,7 @@ await deleteDoc({
 });
 ```
 
-The document must include the current `version` from the latest entry within the satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is particularly useful if your users access your projects simultaneously on multiple devices.
+The document must include the current `version` from the latest entry within the Satellite; otherwise, the call will fail. This prevents unexpected concurrent overwrites, which is particularly useful if your users access your projects simultaneously on multiple devices.
 
 ### Delete multiple documents
 

docs/build/datastore/index.mdx

@@ -38,7 +38,7 @@ In essence, a "Datastore" functions as a keypair store.
 
 ## Limitation
 
-Each satellite has specific memory limits. For detailed information, please refer to the related [documentation](../../miscellaneous/memory.md) page.
+Each Satellite has specific memory limits. For detailed information, please refer to the related [documentation](../../miscellaneous/memory.md) page.
 
 As for documents, they can be up to 2MB in size. However, larger files can be saved in the [storage](build/storage/index.mdx).
 

docs/build/functions/development/components/on-init.mdx

@@ -8,8 +8,8 @@ import styles from "./styles.module.scss";
 ```
 
 <p className={styles.revertMarginTop}>
-  Called during the initialization of the satellite. This hook is invoked when
-  the satellite is first deployed and can be used to set up initial
+  Called during the initialization of the Satellite. This hook is invoked when
+  the Satellite is first deployed and can be used to set up initial
   configurations or resources.
 </p>
 

docs/build/functions/development/components/on-post-upgrade.mdx

@@ -8,7 +8,7 @@ import styles from "./styles.module.scss";
 ```
 
 <p className={styles.revertMarginTop}>
-  Invoked after the satellite has been upgraded to a new version. This hook is
+  Invoked after the Satellite has been upgraded to a new version. This hook is
   typically used to manage migration tasks, or starting custom processes like
   timers.
 </p>

docs/build/functions/index.md

@@ -55,8 +55,8 @@ Custom hooks are not active by default. You need to opt in to enable event-drive
 | `on_delete_asset`           | Storage   | Activated when an asset is deleted.                             |
 | `on_delete_many_assets`     | Storage   | Used for deleting multiple assets.                              |
 | `on_delete_filtered_assets` | Storage   | Invoked when assets are deleted based on filters.               |
-| `on_init`                   | Satellite | Called during the initialization of the satellite.              |
-| `on_post_upgrade`           | Satellite | Invoked after the satellite has been upgraded to a new version. |
+| `on_init`                   | Satellite | Called during the initialization of the Satellite.              |
+| `on_post_upgrade`           | Satellite | Invoked after the Satellite has been upgraded to a new version. |
 
 ---
 

docs/build/hosting/configuration.mdx

@@ -53,7 +53,7 @@ import HttpHeaders from "../components/http-headers.mdx";
 
 By default, all unknown paths are automatically rewritten to `/index.html`. However, if you wish to serve a custom `404 Not Found` error when a user attempts to access a non-existent page, you can do so without requiring additional configuration.
 
-Simply upload a custom `404.html` file to your satellite that should be served from the root path of your site.
+Simply upload a custom `404.html` file to your Satellite that should be served from the root path of your site.
 
 ### Redirects
 

docs/build/hosting/development.md

@@ -9,7 +9,7 @@ This section covers how to configure and manage your custom domain in Juno, incl
 To connect your custom domain, follow these steps:
 
 1. Start the custom domain wizard from the Juno console [hosting](https://console.juno.build/hosting) page
-2. Enter the desired domain name for your satellite
+2. Enter the desired domain name for your Satellite
 3. Log into your domain provider's site and configure the DNS records as indicated by Juno
 4. Continue the process in Juno
 

docs/build/hosting/index.md

@@ -14,7 +14,7 @@ keywords:
 
 Juno Hosting makes it easy to put your project online: fast, secure, and reliable by default.
 
-Deploy your web applications or static sites directly to a satellite using [GitHub Actions](../../guides/github-actions/index.mdx). Your builds run automatically, so shipping updates feels as simple as pushing code.
+Deploy your web applications or static sites directly to a Satellite using [GitHub Actions](../../guides/github-actions/index.mdx). Your builds run automatically, so shipping updates feels as simple as pushing code.
 
 Prefer running things locally? You can also use the [CLI](../../guides/manual-deployment.mdx).