docs: rename package name in imports

Author: w1am

docs/api/persistent-subscriptions.md

@@ -34,7 +34,7 @@ stream, which includes all events.
 ### Subscribing to a Specific Stream
 
 ```ts
-import { persistentSubscriptionToStreamSettingsFromDefaults } from "@eventstore/db-client";
+import { persistentSubscriptionToStreamSettingsFromDefaults } from "@kurrent/kurrentdb-client";
 
 await client.createPersistentSubscriptionToStream(
   "stream-name",
@@ -46,7 +46,7 @@ await client.createPersistentSubscriptionToStream(
 ### Subscribing to `$all`
 
 ```ts
-import { persistentSubscriptionToAllSettingsFromDefaults, streamNameFilter } from "@eventstore/db-client";
+import { persistentSubscriptionToAllSettingsFromDefaults, streamNameFilter } from "@kurrent/kurrentdb-client";
 
 await client.createPersistentSubscriptionToAll(
   "group-name",
@@ -82,7 +82,7 @@ speed of your processing.
 The code below shows how to connect to an existing subscription group for a specific stream:
 
 ```ts
-import { PARK } from "@eventstore/db-client";
+import { PARK } from "@kurrent/kurrentdb-client";
 
 const subscription = client.subscribeToPersistentSubscriptionToStream("stream-name", "group-name");
 
@@ -135,7 +135,7 @@ reason, then you can Nack (not acknowledge) the message and tell the server how
 to handle the failure.
 
 ```ts
-import { PARK } from "@eventstore/db-client";
+import { PARK } from "@kurrent/kurrentdb-client";
 
 const subscription = client.subscribeToPersistentSubscriptionToStream("stream-name", "group-name");
 
@@ -212,7 +212,7 @@ having them reconnect. You must have admin permissions to update a persistent
 subscription group.
 
 ```ts
-import { persistentSubscriptionToStreamSettingsFromDefaults } from "@eventstore/db-client";
+import { persistentSubscriptionToStreamSettingsFromDefaults } from "@kurrent/kurrentdb-client";
 
 await client.updatePersistentSubscriptionToStream(
   "stream-name",

docs/api/reading-events.md

@@ -41,7 +41,7 @@ direction, and revision from which to start. The revision can be specified in se
 - Use `fromRevision` with a specific revision number (64-bit signed integer)
 
 ```ts{2-3}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: FORWARDS,
   fromRevision: START,
   maxCount: 10,
@@ -51,7 +51,7 @@ const events = client.readStream("some-stream", {
 You can also start reading from a specific revision in the stream:
 
 ```ts{3}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: FORWARDS,
   fromRevision: 10,
   maxCount: 10,
@@ -73,7 +73,7 @@ There are a number of additional arguments you can provide when reading a stream
 Passing in the max count allows you to limit the number of events that returned.
 
 ```ts{4}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: FORWARDS,
   fromRevision: START,
   maxCount: 10,
@@ -85,7 +85,7 @@ const events = client.readStream("some-stream", {
 When using projections to create new events you can set whether the generated events are pointers to existing events. Setting this value to true will tell KurrentDB to return the event as well as the event linking to it.
 
 ```ts{4}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: BACKWARDS,
   fromPosition: END,
   resolveLinkTos: true,
@@ -98,7 +98,7 @@ const events = client.readStream("some-stream", {
 The credentials used to read the data can be used by the subscription as follows. This will override the default credentials set on the connection.
 
 ```ts{4-7}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: FORWARDS,
   fromRevision: START,
   credentials: {
@@ -114,7 +114,7 @@ const events = client.readStream("some-stream", {
 In addition to reading a stream forwards, streams can be read backwards. To read all the events backwards, set the `fromRevision` to `END`:
 
 ```ts{2-3}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: BACKWARDS,
   fromRevision: END,
   maxCount: 10,
@@ -138,7 +138,7 @@ It is important to handle this exception when attempting to iterate a stream tha
 For example:
 
 ```ts{12-14}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: FORWARDS,
   fromRevision: 10,
   maxCount: 20,
@@ -228,7 +228,7 @@ const events = client.readAll({
 The credentials used to read the data can be used by the subscription as follows. This will override the default credentials set on the connection.
 
 ```ts{4-7}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: FORWARDS,
   fromRevision: START,
   credentials: {
@@ -245,7 +245,7 @@ In addition to reading the `$all` stream forwards, it can be read backwards. To
 read all the events backwards, set the _direction_ to `BACKWARDS`:
 
 ```ts{2-3}
-const events = client.readStream("some-stream", {
+const events = client.readStream("order-123", {
   direction: BACKWARDS,
   fromRevision: END,
   maxCount: 10,

docs/api/subscriptions.md

@@ -140,7 +140,7 @@ need to store the current position of the subscription somewhere, and then use
 it to restore the subscription from the point where it dropped off:
 
 ```ts{7,14-16}
-import { ReadRevision, START } from "@eventstore/db-client";
+import { ReadRevision, START } from "@kurrent/kurrentdb-client";
 
 let checkpoint: ReadRevision = START;
 
@@ -163,7 +163,7 @@ stream. As mentioned previously, the `$all` stream position consists of two big
 integers (prepare and commit positions), not one:
 
 ```ts{6,13-15}
-import { ReadRevision, START } from "@eventstore/db-client";
+import { ReadRevision, START } from "@kurrent/kurrentdb-client";
 
 let checkpoint: ReadRevision = START;