Fixing merge issue and spelling mistakes

Author: Todd Anderson

packages/shared/common/__tests__/internal/fdv2/PayloadReader.test.ts

@@ -137,7 +137,7 @@ it('it includes multiple types of updates in payload', () => {
   expect(receivedPayloads[0].updates[2].deleted).toEqual(undefined);
 });
 
-it('it does not include messages thats are not between server-intent and payloader-transferred', () => {
+it('it does not include messages thats are not between server-intent and payload-transferred', () => {
   const mockStream = new MockEventStream();
   const receivedPayloads: Payload[] = [];
   const readerUnderTest = new PayloadReader(mockStream, {

packages/shared/common/src/internal/fdv2/payloadReader.ts

@@ -176,7 +176,7 @@ export class PayloadReader {
   private _processPayloadTransferred = (data: PayloadTransferred) => {
     // if the following properties haven't been provided by now, we should reset
     if (
-      !this._tempId || // server intent hasn't been recieved yet.
+      !this._tempId || // server intent hasn't been received yet.
       !data.state ||
       !data.version
     ) {

packages/shared/sdk-server/src/api/options/LDOptions.ts

@@ -70,12 +70,6 @@ export interface LDOptions {
    * Some implementations provide the store implementation object itself, while others
    * provide a factory function that creates the store implementation based on the SDK
    * configuration; this property accepts either.
-   *
-   * @deprecated This is now superceded by {@link LDOptions#dataSystem} using property
-   * {@link LDDataSystemOptions#persistentStore}. The scope of the {@link LDFeatureStore}
-   * that you provide is being reduced in the next major version to only being responsible
-   * for persistence. See documention on {@link LDDataSystemOptions#persistentStore} for
-   * more information.
    */
   featureStore?: LDFeatureStore | ((clientContext: LDClientContext) => LDFeatureStore);
 
@@ -166,11 +160,6 @@ export interface LDOptions {
    *
    * This is true by default. If you set it to false, the client will use polling.
    * Streaming should only be disabled on the advice of LaunchDarkly support.
-   *
-   * @deprecated This functionality is now controlled by {@link LDOptions#dataSystem}
-   * by specifying {@link LDDataSystemOptions#dataSource} options. To opt out of
-   * streaming, you can use the {@link PollingDataSourceOptions}.  Streaming should
-   * only be disabled on the advice of LaunchDarkly support.
    */
   stream?: boolean;
 
@@ -184,12 +173,6 @@ export interface LDOptions {
    * increase exponentially for any subsequent connection failures.
    *
    * The default value is 1.
-   *
-   *
-   * @deprecated This functionality is now controlled by {@link LDOptions#dataSystem}
-   * by specifying {@link LDDataSystemOptions#dataSource} options. Specifying the reconnect
-   * delay is still available when using {@link StandardDataSourceOptions} or
-   * {@link StreamingDataSourceOptions}.
    */
   streamInitialReconnectDelay?: number;
 
@@ -201,9 +184,6 @@ export interface LDOptions {
    * In this configuration, the client will not connect to LaunchDarkly to get feature flags,
    * but will instead get feature state from a database (Redis or another supported feature
    * store integration) that is populated by the relay. By default, this is false.
-   *
-   * @deprecated This functionality is now controlled by {@link LDOptions#dataSystem}
-   * by specifying {@link LDDataSystemOptions#useLdd}.
    */
   useLdd?: boolean;