DOCSP-10976 partial id strategy (#51)

* DOCSP-10976: Update PartialKey id strategies

Author: Chris Cho

source/kafka-sink-postprocessors.txt

@@ -707,7 +707,7 @@ using data contained within multiple fields in the record as well as
 instructs the post processor to generate *BSON ObjectIds* for inserts,
 but not for updates.
 
-The following steps are required to configure this strategy:
+Follow the steps below to configure this strategy:
 
 #. Create a :manual:`unique index </core/index-unique>` that corresponds to
    your business key in your target MongoDB collection.
@@ -718,8 +718,8 @@ The following steps are required to configure this strategy:
    ``ReplaceOneBusinessKeyStrategy`` writemodel strategy.
 
 For this example, we track airplane capacity by the flight number and
-airport it is currently located represented by ``flight_no`` and
-``airport_code``, respectively. An example message contains the following:
+airport location represented by ``flight_no`` and ``airport_code``,
+respectively. An example message contains the following:
 
 .. code-block:: json
 
@@ -732,7 +732,7 @@ airport it is currently located represented by ``flight_no`` and
      }
    }
 
-In order to implement the strategy, we first create a unique index on the
+To implement the strategy, we first create a unique index on the
 ``flight_no`` and ``airport_code`` fields in the MongoDB shell:
 
 .. code-block:: none
@@ -747,8 +747,8 @@ file:
 .. code-block:: properties
 
    document.id.strategy=com.mongodb.kafka.connect.sink.processor.id.strategy.PartialValueStrategy
-   value.projection.list=flight_no,airport_code
-   value.projection.type=AllowList
+   document.id.strategy.partial.value.projection.list=flight_no,airport_code
+   document.id.strategy.partial.value.projection.type=AllowList
    writemodel.strategy=com.mongodb.kafka.connect.sink.writemodel.strategy.ReplaceOneBusinessKeyStrategy"
 
 The sample data inserted into the collection contains the following:
@@ -783,18 +783,6 @@ values without changing the ``_id`` field.
      }
    }
 
-.. admonition:: Projection post processors are not compatible with PartialValueStrategy
-   :class: warning
-
-   The ``PartialValueStrategy`` id strategy uses the
-   ``[key|value].projection.type`` and ``[key|value].projection.list``
-   settings to define which fields are used to form the ``_id`` field.
-   Since the Block List and Allow List post processors use the same
-   projection settings, they cannot be specified separately. Use a `Single
-   Message Transform (SMT)
-   <https://docs.confluent.io/current/connect/transforms/index.html>`_
-   outside the connector to format your source data as necessary.
-
 .. _writemodel-strategy-timestamps:
 
 WriteModel Strategy: Inserted and Modified Timestamps