addressed feedback

Author: jlquaccia

dev-docs/modules/previousAuctionInfo.md

@@ -35,7 +35,7 @@ If the requirements above are met, the flow for how the module works is as follo
 1. A Prebid.js auction runs and completes.
 1. At the end of an auction, details about the auction are collected from each bidder using the module.
 1. If a Prebid bid wins, then the `rendered` field is updated to `1` to indicate this in the collected auction data for all bidders who bid on the same adunit within the same Prebid auction.
-1. During the next Prebid.js auction, if a bidder has this module enabled AND submits a valid bid request, then previous auction info data will be injected into the bidder's bid request of the new auction within the following path: `ortb2.ext.prebid.previousauctioninfo`.
+1. During the next Prebid.js auction, if a bidder is included in previousAuctionInfo.bidders AND is included in the auction, then previous auction info data will be injected into the bidder's bid request of the new auction within the following path: `ortb2.ext.prebid.previousauctioninfo`.
 
 ## Configuration Options
 

dev-docs/publisher-api-reference/setConfig.md

@@ -1404,18 +1404,6 @@ pbjs.setConfig({
 
 <a name="setConfig-Generic-Configuration"></a>
 
-### Enable Previous Auction Info
-
-The Previous Auction Info module enables functionality to collect prior auction data for participating bidders and publishers (This feature is `opt-in`, by default it is disabled).
-
-```javascript
-pbjs.setConfig({previousAuctionInfo: { enabled: true, bidders: ['bidderCode1', 'bidderCode2'], maxQueueLength: 10 }})
-```
-
-Note: The `enabled` field is required, the `bidders` and `maxQueueLength` fields are not. For more information about this module, see: [Previous Auction Info](https://docs.prebid.org/dev-docs/modules/previousAuctionInfo.html).
-
-<a id="setConfig-previousAuctionInfo"></a>
-
 ### General adapter Configuration
 
 Some adapters may support other options, as defined in their documentation. To set arbitrary configuration values: