Spelling corrections

Author: blowdart

docs/docs/code/helloWorld.cs

@@ -1,5 +1,5 @@
 using idunno.Bluesky;
 
 using BlueskyAgent agent = new();
-var loginResult = await agent.Login(handle, password);
+await agent.Login(handle, password);
 await agent.Post("Hello World from idunno.Bluesky");

docs/docs/commonTerms.md

@@ -27,7 +27,7 @@ A `StrongReference` is a record contain both the [at:// uri](#uri) of a record,
 
 Bluesky stores all your stuff in a repository on a Personal Data Server (PDS).
 A repository contains various collections, and these collections contain records.
-For example, when you write a post you are cerating a record in your repository in the `app.bsky.feed.post` collection.
+For example, when you write a post you are creating a record in your repository in the `app.bsky.feed.post` collection.
 
 A simple post record would, in JSON, look something like this
 
@@ -63,21 +63,30 @@ The Bluesky API documentation refers to a user or bot account as an`Actor`. Acto
 
 ### <a name="handles">Handles</a>
 
-A `handle` is what you see in human readable terms, for example "blowdart.me". It's how you view a profile in the browser, for example https://bsky.app/profile/blowdart.me and it's how you @ people in posts.
+A `handle` is what you see in human readable terms, for example "blowdart.me". It's how you view a profile in the browser, for example https://bsky.app/profile/blowdart.me and
+it's how you @ people in posts.
 
-However as you may have discovered handles can change. When registering on Bluesky you register with a *something*.bsky.social handle, which you can then change to be DNS "verified". If you change your handle your posts still remain, and people that follow you keep following you through the change. This is because underneath handles aren't often used by the APIs, an account is referenced by its `DID`.
+However as you may have discovered handles can change. When registering on Bluesky you register with a *something*.bsky.social handle, which you can then change to be DNS "verified".
+If you change your handle your posts still remain, and people that follow you keep following you through the change. This is because underneath handles aren't often used by the APIs,
+an account is referenced by its `DID`.
 
 ### <a name="dids">Distributed Identifier (DID)</a>
 
-A `DID` is your unique key on the atproto network. Under the covers Bluesky uses `DID`s, not handles for pretty much everything, sometimes accepting both and doing the work behind the scenes to resolve a handle into a `DID``.
+A `DID` is your unique key on the atproto network. Under the covers Bluesky uses `DID`s, not handles for pretty much everything, sometimes accepting both and doing the
+work behind the scenes to resolve a handle into a `DID``.
 
-A `DID` looks something like this: `did:plc:hfgp6pj3akhqxntgqwramlbg`. The first part of the `DID` is the prefix declaring it's a `DID`, the second part is an identifier for the issuer (`plc` is a `DID` issued by Bluesky, `web` is another common identifier indicating an independently issued `DID`), and the final part is a unique reference issued by the issuer.
+A `DID` looks something like this: `did:plc:hfgp6pj3akhqxntgqwramlbg`. The first part of the `DID` is the prefix declaring it's a `DID`,
+the second part is an identifier for the issuer (`plc` is a `DID` issued by Bluesky, `web` is another common identifier indicating an independently issued `DID`),
+and the final part is a unique reference issued by the issuer.
 
-For example, the api to [get an actor profile](https://docs.bsky.app/docs/api/app-bsky-actor-get-profile) takes a `DID`or a handle (this either/or combination is represented as an At-Identifier), but things like [updateAccountPassword](https://docs.bsky.app/docs/api/com-atproto-admin-update-subject-status) take just a `DID`.
+For example, the api to [get an actor profile](https://docs.bsky.app/docs/api/app-bsky-actor-get-profile) takes a `DID`or a handle
+(this either/or combination is represented as an At-Identifier), but things like [updateAccountPassword](https://docs.bsky.app/docs/api/com-atproto-admin-update-subject-status) take just a `DID`.
 
 When you login via an agent the authenticated user's `DID` is available via the `Did` property on the agent instance.
 
-Bluesky's `DID` directory is available at https://web.plc.directory/. It servers up a `DidDoc` for a plc `DID` which allows discovery of things like a `DID`'s personal data server where authenticated API calls should go. The `BlueskyAgent` class take care of PDS discovery automatically, but you can retrieve a `DidDoc` yourself using the `DirectoryAgent` `ResolveDidDocument` method.
+Bluesky's `DID` directory is available at https://web.plc.directory/. It servers up a `DidDoc` for a plc `DID` which allows discovery of things like a `DID`'s personal data
+server where authenticated API calls should go. The `BlueskyAgent` class take care of PDS discovery automatically,
+but you can retrieve a `DidDoc` yourself using the `DirectoryAgent` `ResolveDidDocument` method.
 
 ### <a name="resolvingHandles">Resolving a Handle to a DID</a>
 
@@ -87,7 +96,8 @@ The `AtProto` and `Bluesky` agents provide a method to resolve a `DID` for a `Ha
 
 As you explore the APIs you while you write records you don't get records, instead you get views of records. You create a `Post` but what you see in your timeline is a `PostView`.
 
-A view is how Bluesky aggregates information from multiple records into a single entity. For example a `PostView` takes information from not only the `Post` record, but also information about the post author via a `ProfileView`, and things like reply and like counts. If you've used a SQL database before you can think of a view like a select over multiple joined tables.
+A view is how Bluesky aggregates information from multiple records into a single entity. For example a `PostView` takes information from not only the `Post` record,
+but also information about the post author via a `ProfileView`, and things like reply and like counts.
+If you've used a SQL database before you can think of a view like a select over multiple joined tables.
 
 Views are generated by applications, the overall view over data that Bluesky presents is commonly referred to as the `AppView`.
-

docs/docs/conversationsAndMessages.md

@@ -45,7 +45,8 @@ foreach (MessageViewBase message in getMessages.Result)
 }
 ```
 
-Once you've shown a user their messages you can update the read status of a conversation with `UpdateRead()` which takes the conversation id, and, optionally the message id of the last message seen.
+Once you've shown a user their messages you can update the read status of a conversation with `UpdateRead()` which takes the conversation id, and,
+optionally the message id of the last message seen.
 
 ## <a name="sending">Sending a message</a>
 

docs/docs/notifications.md

@@ -6,7 +6,8 @@ Like the [timeline sample](timeline.md) notifications can be retrieved and itera
 HttpResult<int> unreadCount = await agent.GetNotificationUnreadCount();
 ```
 
-`GetNotificationUnreadCount()` allows you to check if there's anything unread before you consider retrieving notifications. This could also be used for an indicator in an application or badge. `GetNotificationUnreadCount()` also takes an optional `DateTimeOffset` parameter to allow you to get the unread count from a particular date and time.
+`GetNotificationUnreadCount()` allows you to check if there's anything unread before you consider retrieving notifications. This could also be used for an indicator in an application or badge.
+`GetNotificationUnreadCount()` also takes an optional `DateTimeOffset` parameter to allow you to get the unread count from a particular date and time.
 
 To retrieve your notifications, read or unread, you call `ListNotifications()`.
 
@@ -15,7 +16,7 @@ var notifications =
     await agent.ListNotifications().ConfigureAwait(false);
 ```
 
-From there, you would perform the `.Succeded` check and work your way through the notifications collection exposed in the `Result` property. Each notification has a reason property. 
+From there, you would perform the `.Succeded` check and work your way through the notifications collection exposed in the `Result` property. Each notification has a reason property.
 
 Each type of notification, `Follow`, `Like`, `Mention`, `Quote`, `Reply`, and `Repost` having varying types of information used to supplement the notification with appropriate information.
 
@@ -76,13 +77,18 @@ HttpResult<EmptyResponse> updateSeen =
     await agent.UpdateNotificationSeenAt();
 ```
 
-`UpdateNotificationSeenAt()` takes an optional `DateTimeOffset seenAt` parameter, so you can, and probably should, save a timestamp before you start working through notifications, and then use the saved timestamp once you've finished, so that notifications that happen after you retrieved the notification list don't get marked as seen. `UpdateNotificationSeenAt()` can also take a `seenAt` parameter in the past, which allows you to reset when Bluesky things you last saw notifications - which is very handy for testing any notification viewer you've written.
+`UpdateNotificationSeenAt()` takes an optional `DateTimeOffset seenAt` parameter, so you can, and probably should, save a timestamp before you start working through notifications,
+and then use the saved timestamp once you've finished, so that notifications that happen after you retrieved the notification list don't get marked as seen.
+`UpdateNotificationSeenAt()` can also take a `seenAt` parameter in the past, which allows you to reset when Bluesky things you last saw notifications, which is very handy
+for testing any notification viewer you've written.
 
-A full sample can be found in the [Notifications](https://github.com/blowdart/idunno.atproto/tree/main/samples/Samples.Notifications) project in the [samples](https://github.com/blowdart/idunno.atproto/tree/main/samples) directory in this GitHub repository.
+A full sample can be found in the [Notifications](https://github.com/blowdart/idunno.atproto/tree/main/samples/Samples.Notifications) project in the
+[samples](https://github.com/blowdart/idunno.atproto/tree/main/samples) directory in this GitHub repository.
 
 ## <a name=cursorsPagination>Cursors and Pagination</a>
 
-If you've looked at the source code for the [Notifications sample](https://github.com/blowdart/idunno.atproto/tree/main/samples/Samples.Notifications)  you may have noticed it pages through notifications rather than get all the notifications at once.
+If you've looked at the source code for the [Notifications sample](https://github.com/blowdart/idunno.atproto/tree/main/samples/Samples.Notifications) you may have noticed it pages
+through notifications rather than get all the notifications at once.
 
 The sample uses the `limit` and `cursor` parameters to get notifications one page at a time, consisting of five notifications per page.
 

docs/docs/posting.md

@@ -384,7 +384,8 @@ var builderPostResult = await agent.Post(postBuilder, cancellationToken: cancell
 
 ## <a name="openGraphCards">Embedding an external link (Open Graph cards)</a>
 
-[Open Graph](https://ogp.me/) is a standard that allows web pages to become a rich object in a social graph. Open Graph metadata allows you to embed a rich link card in a Bluesky post, which will look something like this:
+[Open Graph](https://ogp.me/) is a standard that allows web pages to become a rich object in a social graph. Open Graph metadata allows you to embed a rich link card in a
+Bluesky post, which will look something like this:
 
 ![An embedded link to Wikipedia's page on Baked Beans](media/embeddedCard.png "An embedded Card")
 
@@ -404,8 +405,8 @@ If you don't want to use a `PostBuilder` you can use the appropriate `Post()` me
 var postResult = agent.Post(externalCard: embeddedExternal, cancellationToken: cancellationToken);
 ```
 
-You can use libraries like [OpenGraph.net](https://github.com/ghorsey/OpenGraph-Net/) or [X.Web.MetaExtractor](https://www.nuget.org/packages/X.Web.MetaExtractor) to retrieve Open Graph properties from which you can construct a card.
-For example, using OpenGraph.Net
+You can use libraries like [OpenGraph.net](https://github.com/ghorsey/OpenGraph-Net/) or [X.Web.MetaExtractor](https://www.nuget.org/packages/X.Web.MetaExtractor) to retrieve
+Open Graph properties from which you can construct a card. For example, using OpenGraph.Net
 
 ```
 Uri pageUri = new ("https://en.wikipedia.org/wiki/Baked_beans");

docs/docs/profileEditing.md

@@ -2,7 +2,8 @@
 
 A user's profile consists of the user's title, a description, a profile picture and a banner picture, all of which can be left empty, as
 well as other settings like a pinned post that is shown when someone views the account's profile page, a setting to discourage applications
-for displaying the profile and posts to unauthenticated users and self labels, which can be any of the configuration [global label values](https://docs.bsky.app/docs/advanced-guides/moderation#global-label-values).
+for displaying the profile and posts to unauthenticated users and self labels,
+which can be any of the configuration [global label values](https://docs.bsky.app/docs/advanced-guides/moderation#global-label-values).
 
 To get the profile record for the current user call `agent.GetProfileRecord()`.
 

docs/docs/profiles.md

@@ -23,7 +23,7 @@ Profile views can include labels from labelers. Please see [Labels](labels.md) f
 
 ## <a name="profileVerification">Profile verification</a>
 
-Bluesky supports a composible verification system where various organications will verify accounts, for example the New York Times may verify their reporters. The
+Bluesky supports a composable verification system where various organizations will verify accounts, for example the New York Times may verify their reporters. The
 `Verification` property holds the verification status for a user, and a list of the verifiers who have verified it. The `VerifiedStatus` can be valid, invalid, none or unknown,
 you can use this to decide if you want to display an indicator of the status to your users.
 

docs/docs/requestsAndResponses.md

@@ -1,7 +1,7 @@
 # <a name="makingRequests">Making requests to Bluesky</a>
 
-Making requests to Bluesky is done though the `BlueskyAgent` class. Once you authenticate using `agent.Login()` or via OAuth,
-the agent manages your "session"", the tokens necessary to make authenticated requests are stored, refreshed automatically
+Making requests to Bluesky is done though the `BlueskyAgent` class. Once you authenticate using `agent.Login()` or via [OAuth](connecting.md#oauth),
+the agent manages your "session", the tokens necessary to make authenticated requests are stored, refreshed automatically
 and added to any authenticated API requests.
 
 ## <a name="understandingResults">Understanding responses from Bluesky</a>
@@ -11,9 +11,9 @@ avoids the use of exceptions should the HTTP call fail, and allows you to view a
 
 `AtProtoHttpResult<T>` has properties to help you determine the success or failure of the call. These include
 
-* The `Succeeded` property, a `boolean` indicated whether the API call was sucessful or not,
+* The `Succeeded` property, a `boolean` indicated whether the API call was successful or not,
 * The `StatusCode` property containing the HTTP status code from the API call,
-* The `Result` property, containing the result of the API call. This may be null if a call was unsucessful,
+* The `Result` property, containing the result of the API call. This may be null if a call was unsuccessful,
 * The `AtErrorDetail` property, containing any detailed error messages from the API if any were returned.
 
 If a request is **successful** the `Succeeded` property on the returned result instance will be `true`, the `Result` property will not be null, and
@@ -40,8 +40,6 @@ Let's add some basic error checking to the Hello World code you wrote in [gettin
 * Lines 13-16 show a reaction if the call to `Post()` failed, and
 * Lines 19-25 show how you can check for any API errors that might be returned.
 
-You can download [helloWorldErrorChecked.cs](./code/helloWorldErrorChecked.cs).
-
 > [!TIP]
 > `AtProtoHttpResult<T>` has an `EnsureSucceeded()` method which will throw an `AtProtoHttpRequestException` if the `Succeeded` property is false.
 > This can be used while testing code, or even during development before you implement error handling.

docs/docs/sourceGeneration.md

@@ -112,7 +112,7 @@ For example, if you have a custom `AtProtoRecordValue` and corresponding `AtProt
 
 Native AOT has benefits:
 
-* Reduced disk footprint: Native AOT publishing produces a single executable containing just the code from exteneral dependencies that is used by your application.
+* Reduced disk footprint: Native AOT publishing produces a single executable containing just the code from external dependencies that is used by your application.
 * Reduced startup time: Native AOT can show reduced start-up times, meaning your app is ready to respond more quickly.
 * Reduced memory usage: Native AOT apps can show reduced memory demands, depending on the work it does.
 

docs/docs/tutorials/creatingAPost.md

@@ -62,7 +62,7 @@ Reply and quote posts contain [strong references](../commonTerms.md#strongRefere
 
 Replies and quote posts contain strong references to other records.
 
-* [at:// uri](../commonTerms.md#uri): indicating the repositody DID, collection and record key
+* [at:// uri](../commonTerms.md#uri): indicating the repository [DID](../commonTerms.md#dids), collection and record key
 * [CID](../commonTerms.md#cid): the hash to the record itself
 
 You can get a post's strong reference from the timeline view, author view or other views that contain posts like search views or feed views.