fix: PR comment updates

Author: Kai-ros

docs/content/4.integrations/1.atmosphere.md

@@ -13,7 +13,7 @@ _npmx.dev_ site architecture as it pertains to the ATProtocol (ATProto) ecosyste
 
 ## Atmosphere
 
-The Atmosphere is the interconnected web of applications that all run on the ATProto. The primary benefits of this integration for _npmx.dev_ are the social features that connect us to the tens of millions of users on the ATProto social graph. Per the docs site:
+The Atmosphere is the interconnected web of applications that all run on ATProto. The primary benefits of this integration for _npmx.dev_ are the social features that connect us to the tens of millions of users on the ATProto social graph. Per the docs site:
 
 > The AT Protocol is an open, decentralized network for building social applications.
 
@@ -23,7 +23,7 @@ The Atmosphere is the interconnected web of applications that all run on the ATP
 
 These are the essential components that allow for _npmx.dev_ to exist as an app on the Atmosphere:
 
-1. **App View** - _npmx.dev_ site
+1. **Domain** - _npmx.dev_ site
 2. **OAuth** - Required for interacting with the Atmosphere
 3. **Constellation** - A global atproto backlink index
 4. **Lexicons** - Schema definition language
@@ -33,7 +33,7 @@ These are the essential components that allow for _npmx.dev_ to exist as an app
 
 For more details refer to the official ATProto docs [here](https://atproto.com/guides/the-at-stack).
 
-### App View
+### Domain
 
 The _npmx.dev_ app is the frontend domain for the site which acts as a third-party browser for the extant [npmjs site](https://www.npmjs.com) but prioritized around high developer experience (DX) and native-like performance. As it concerns the idiomatic Atmosphere stack, it serves as the client entry point and enables user controls for `@npmx.social` profiles.
 
@@ -51,12 +51,16 @@ For more details refer to the official ATProto docs [here](https://atproto.com/s
 
 Constellation serves as the API orchestration layer and backend indexer. It acts as a bridge between _npmx.dev_ specific data structures and the wider ATProto network. Specifically, it indexes backlinks, aggregates app-view data, and manages the caching layer to reduce load on individual PDS instances during high-traffic events.
 
+For more details refer to the official Constellation site [here](https://constellation.microcosm.blue/).
+
 ### Lexicons
 
 This is the glue that makes _npmx.dev_ data understandable to other ATProto apps. We utilize custom Lexicons to define the schema for _npmx.dev_ specific record types, such as our social features, package reviews, or documentation comments.
 
 > Lexicon is a schema definition language used to describe atproto records, HTTP endpoints (XRPC), and event stream messages.
 
+For the _npmx.dev_ specific implementation you can see them in the repo [here](https://atproto.com/specs/lexicon) and as they become more fixed we will publish their accompanying schemas.
+
 For more details refer to the official ATProto docs [here](https://atproto.com/specs/lexicon).
 
 ### Personal Data Servers (PDS)
@@ -71,7 +75,9 @@ For more details refer to the official ATProto docs [here](https://atproto.com/g
 
 ### Standard Site Sync
 
-The mechanism for ensuring state consistency between _npmx.dev_ and our self-hosted PDS. Standard Site Sync acts as a specialized repository synchronization layer that translates changes from the _npmx.dev_ platform, such as when we publish a new blog post in the form of a Markdown file, into valid ATProto records that are then pushed to a user's PDS. This ensures that content created on _npmx.dev_ lives permanently in the user's data repository.
+Standard Site Sync acts as a specialized repository synchronization layer that translates changes from the _npmx.dev_ platform, such as when we publish a new blog post in the form of a Markdown file, into valid ATProto records that are then pushed to a user's PDS. It is the mechanism for maintaining state consistency between _npmx.dev_ and our self-hosted PDS, which ensures that content created on _npmx.dev_ lives permanently in the user's data repository.
+
+For more details refer to the official Standard Site [here](https://standard.site).
 
 ### Bluesky Social Graph