docs: fix typos by codex

adops/mobile-rendering-max-line-item-setup.md

@@ -37,7 +37,7 @@ Create or choose an existing Ad Unit. Go the the `Custom Networks & Deals` secti
 
 <img src="/assets/images/prebid-mobile/modules/rendering/max-ad-unit-setup.png" alt="Pipeline Screenshot" align="center">
 
-Make sure that the `Custom Parameters` field contains expecting targetting keywords of the winning bid:
+Make sure that the `Custom Parameters` field contains the expected targeting keywords of the winning bid:
 
 ```json
 {"hb_pb":"0.10"}

dev-docs/bidders/deepintent.md

@@ -88,6 +88,7 @@ var adUnits = [
 Deepintent supports video as of Prebid v1.16.0
 
 {: .table .table-bordered .table-striped }
+
 | Name                      | Scope    | Description                                                  | Example |
 | :----------------------| :------- | :---------------------------------------------------------- | :------ |
 | `video.mimes`          | required | Video MIME types                                               | `['video/mp4','video/x-flv']` |
@@ -101,7 +102,7 @@ Deepintent supports video as of Prebid v1.16.0
 | `video.battr`          | optional | Blocked creative attributes, See [OpenRTB 2.5 specification](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf), List 5.3 for values             | `[3, 9]` |
 | `video.linearity`      | optional | Indicates if the impression is linear or nonlinear<br/>Values:<br/>`1`: Linear/In-Stream<br/>`2`: Non-Linear/Overlay.                                                                                | `1` |
 | `video.placement`      | optional | Video placement type.  See [OpenRTB 2.5 specification](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf), List 5.9 for Values                            | `1` |
-| `video.minbitrate`      | optional | Minumim bit rate in Kbps.                                   | 50 |
+| `video.minbitrate`      | optional | Minimum bit rate in Kbps.                                   | 50 |
 | `video.maxbitrate`      | optional | Maximum bit rate in Kbps.                                   | 70 |
 
 ### AdUnit Format for Video

dev-docs/bidders/pubmatic.md

@@ -32,6 +32,7 @@ endpoint_compression: true
 ### Bid Params
 
 {: .table .table-bordered .table-striped }
+
 | Name          | Scope    | Description        | Example                      | Type     |
 |---------------|----------|--------------------|------------------------------|----------|
 | `publisherId` | required | Publisher ID       | `'32572'`                    | `string` |
@@ -74,6 +75,7 @@ Note: Combine the above the configuration with any other UserSync configuration.
 The adSlot parameter supports two different formats:
 
 {: .table .table-bordered .table-striped }
+
 | Format         | Example              |
 |----------------|----------------------|
 | Without Size   | `'38519891'`         |
@@ -86,6 +88,7 @@ adSlot parameter is optional.  To omit the adSlot parameter, your publisher acco
 The PubMatic adapter supports video as of Prebid v1.16.0
 
 {: .table .table-bordered .table-striped }
+
 | Name                      | Scope    | Description                                              | Example |
 | :----------------------| :------- | :---------------------------------------------------------- | :------ |
 | `video.mimes`          | required | Video MIME types                                            | `['video/mp4','video/x-flv']` |
@@ -100,7 +103,7 @@ The PubMatic adapter supports video as of Prebid v1.16.0
 | `video.linearity`      | optional | Indicates if the impression is linear or nonlinear<br/>Values:<br/>`1`: Linear/In-Stream<br/>`2`: Non-Linear/Overlay.                                                                                | `1` |
 | `video.placement`      | optional | Video placement type.  See [OpenRTB 2.5 specification](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf), List 5.9 for Values                            | `1` |
 | `video.plcmt`          | optional | Video placement type. See [OpenRTB 2.6 specification - github](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/develop/2.6.md#327---object-video-), For values [plcmt subtypes](https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/develop/AdCOM%20v1.0%20FINAL.md#list_plcmtsubtypesvideo)                            | `1` |
-| `video.minbitrate`     | optional | Minumim bit rate in Kbps.                                   | 50 |
+| `video.minbitrate`     | optional | Minimum bit rate in Kbps.                                   | 50 |
 | `video.maxbitrate`     | optional | Maximum bit rate in Kbps.                                   | 70 |
 
 ### AdUnit Format for Video

dev-docs/bidders/pwbid.md

@@ -27,6 +27,7 @@ The PubWise bid adapter is now availalbe self service. Visit <http://www.PubWise
 siteID is sufficient for bidding.
 
 {: .table .table-bordered .table-striped }
+
 | Name         | Scope    | Description                                                                                       | Example                  | Type      |
 |--------------|----------|---------------------------------------------------------------------------------------------------|--------------------------|-----------|
 | `siteId`     | required | The site ID provided by the PubWise system                                                       | `'XXXXXX'`               | `string`  |
@@ -38,6 +39,7 @@ siteID is sufficient for bidding.
 The PubWise adapter supports video as of Prebid v7.39.0. Outstream is NOT supported currently.
 
 {: .table .table-bordered .table-striped }
+
 | Name                      | Scope    | Description                                                  | Example |
 | :----------------------| :------- | :---------------------------------------------------------- | :------ |
 | `video.mimes`          | required | Video MIME types                                               | `['video/mp4','video/x-flv']` |
@@ -51,7 +53,7 @@ The PubWise adapter supports video as of Prebid v7.39.0. Outstream is NOT suppor
 | `video.battr`          | optional | Blocked creative attributes, See [OpenRTB 2.5 specification](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf), List 5.3 for values             | `[3, 9]` |
 | `video.linearity`      | optional | Indicates if the impression is linear or nonlinear<br/>Values:<br/>`1`: Linear/In-Stream<br/>`2`: Non-Linear/Overlay.                                                                                | `1` |
 | `video.placement`      | optional | Video placement type.  See [OpenRTB 2.5 specification](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf), List 5.9 for Values                            | `1` |
-| `video.minbitrate`      | optional | Minumim bit rate in Kbps.                                   | 50 |
+| `video.minbitrate`      | optional | Minimum bit rate in Kbps.                                   | 50 |
 | `video.maxbitrate`      | optional | Maximum bit rate in Kbps.                                   | 70 |
 
 ### Example

dev-docs/modules/floors.md

@@ -369,7 +369,7 @@ You **cannot** set the `floorMin` parameter without specifying a `data` object.
 | data.floorProvider | string | Optional atribute (as of prebid version 4.2) used to signal to the Floor Provider's Analytics adapter their floors are being applied. They can opt to log only floors that are applied when they are the provider. If floorProvider is supplied in both the top level of the floors object and within the data object, the data object's configuration shall prevail.| - |
 | data.currency | string | Currency of floor data. Floor Module will convert currency where necessary. See Currency section for more details. | 'USD' |
 | data.skipRate | integer | skipRate is a random function whose input value is any integer 0 through 100 to determine when to skip all floor logic, where 0 is always use floor data and 100 is always skip floor data. The use case is for publishers or floor providers to learn bid behavior when floors are applied or skipped. Analytics adapters will  have access to model version (if defined) when skipped is true to signal the Price Floors Module is in floors mode. If skipRate is supplied in both the root level of the floors object and within the data object, the skipRate configuration within the data object shall prevail. | 0 |
-| data.floorsSchemaVersion | integer | The module supports two versions of the data schema. Version 1 allows for only one model to be applied in a given data set, whereas Version 2 allows you to sample multiple models selected by supplied weights. If no schema version is provided, the module will assume version 1 for the sake of backwards compatiblity. For schema version 2 see the next section. | 1 |
+| data.floorsSchemaVersion | integer | The module supports two versions of the data schema. Version 1 allows for only one model to be applied in a given data set, whereas Version 2 allows you to sample multiple models selected by supplied weights. If no schema version is provided, the module will assume version 1 for the sake of backwards compatibility. For schema version 2 see the next section. | 1 |
 | data.modelVersion | string | Used by floor providers to train on model version performance. The expectation is a floor provider’s analytics adapter will pass the model verson back for algorithm training. | - |
 | data.modelTimestamp | integer | Epoch timestamp associated with modelVersion. Can be used to track model creation of floor file for post auction analysis.| - |
 | data.schema | object |allows for flexible definition of how floor data is formatted. | - |
@@ -436,7 +436,7 @@ You **cannot** set the `floorMin` parameter without specifying a `data` object.
 | data.currency | string | Currency of floor data. The module will convert currency where necessary. See Currency section for more details. | 'USD' |
 | data.skipRate | integer | skipRate is a random function whose input value is any integer 0 through 100 to determine when to skip all floor logic, where 0 is always use floor data and 100 is always skip floor data. The use case is for publishers or floor providers to learn bid behavior when floors are applied or skipped. Analytics adapters will  have access to model version (if defined) when skipped is true to signal the module is in floors mode. If skipRate is supplied in both the root level of the floors object and within the data object, the skipRate configuration within the data object shall prevail.| 0 |
 | data.useFetchDataRate | integer | (PBS-Go 2.6+) useFetchDataRate is a random function whose input value is any integer 0 through 100 to determine when to skip dynamic floor data and fall back to static floor data. 0 means always use static floor data and 100 means always use dynamic floor data. The use case is for publishers or floor providers to confirm how dynamic floors data compares to static floors data. Analytics adapters will have access to the location of the actual floors data used, either "request" or "fetch". | 100 |
-| data.floorsSchemaVersion | integer | The module supports two version of the data schema. Version 1 allows for only one model to be applied in a given data set, whereas Version 2 allows you to sample multiple models selected by supplied weights. If no schema version is provided, the module will assume version 1 for the sake of backwards compatiblity.| 1 |
+| data.floorsSchemaVersion | integer | The module supports two versions of the data schema. Version 1 allows for only one model to be applied in a given data set, whereas Version 2 allows you to sample multiple models selected by supplied weights. If no schema version is provided, the module will assume version 1 for the sake of backwards compatibility.| 1 |
 | data.modelTimestamp | int | Epoch timestamp associated with modelVersion. Can be used to track model creation of floor file for post auction analysis.| - |
 | data.noFloorSignalBidders | array of strings | (PBJS 8.31+, PBS-Java 3.4+) This is an array of bidders for which to avoid sending floors. This is useful for bidders where the publishers has established different floor rules in their systems. The value can be `["*"]`. | - |
 | data.modelGroups | array of objects | Array of model objects to be used for A/B sampling multiple models. This field is only used when data.floorsSchemaVersion = 2 | - |

guide/pb-guide-alerts.md

@@ -134,4 +134,4 @@ For example, if you had content such as "The adpod unit is only available for lo
 
 {% include alerts/alert_note.html content="The adpod unit is only available for long-form video." %}
 
-Use the Liquid `capture` command when you are creating an alert that is very long or contains HTML formating.
+Use the Liquid `capture` command when you are creating an alert that is very long or contains HTML formatting.

prebid-mobile/modules/rendering/android-sdk-integration-admob.md

@@ -85,7 +85,7 @@ This step is the same as for the original [AdMob integration](https://developers
 #### Step 2: Create AdMobMediationBannerUtils
 {:.no_toc}
 
-The `AdMobBannerMediationUtils` is a helper class, which performs certain utilty work for the `MediationBannerAdUnit`, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
+The `AdMobBannerMediationUtils` is a helper class, which performs certain utility work for the `MediationBannerAdUnit`, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
 
 #### Step 3: Create MediationBannerAdUnit
 {:.no_toc}
@@ -153,7 +153,7 @@ This step is the same as for original [AdMob integration](https://developers.goo
 #### Step 2: Create AdMobInterstitialMediationUtils
 {:.no_toc}
 
-The `AdMobInterstitialMediationUtils` is a helper class, which performs certain utilty work for the `MediationInterstitialAdUnit`, like passing the targeting keywords to adapters.
+The `AdMobInterstitialMediationUtils` is a helper class, which performs certain utility work for the `MediationInterstitialAdUnit`, like passing the targeting keywords to adapters.
 
 #### Step 3: Create MediationInterstitialAdUnit
 {:.no_toc}
@@ -240,7 +240,7 @@ This step is the same as for the original [AdMob integration](https://developers
 ##### Step 2: Create AdMobRewardedMediationUtils
 {:.no_toc}
 
-The `AdMobRewardedMediationUtils` is a helper class, which performs certain utilty work for the `MediationInterstitialAdUnit`, like passing the targeting keywords to adapters.
+The `AdMobRewardedMediationUtils` is a helper class, which performs certain utility work for the `MediationInterstitialAdUnit`, like passing the targeting keywords to adapters.
 
 ##### Step 3: Create MediationRewardedVideoAdUnit
 {:.no_toc}

prebid-mobile/modules/rendering/android-sdk-integration-max.md

@@ -74,7 +74,7 @@ This step is totally the same as for original [MAX integration](https://dash.app
 #### Step 2: Create MaxMediationBannerUtils
 {:.no_toc}
 
-The `MaxMediationBannerUtils` is a helper class, which performs certain utilty work for the `MediationBannerAdUnit`, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
+The `MaxMediationBannerUtils` is a helper class, which performs certain utility work for the `MediationBannerAdUnit`, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
 
 #### Step 3: Create MediationBannerAdUnit
 {:.no_toc}
@@ -139,7 +139,7 @@ This step is totally the same as for original [MAX integration](https://dash.app
 #### Step 2: Create MaxMediationInterstitialUtils
 {:.no_toc}
 
-The `MaxMediationInterstitialUtils` is a helper class, which performs certain utilty work for the `MediationInterstitialAdUnit`, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
+The `MaxMediationInterstitialUtils` is a helper class, which performs certain utility work for the `MediationInterstitialAdUnit`, like passing the targeting keywords to the adapters and checking the visibility of the ad view.
 
 #### Step 3: Create MediationInterstitialAdUnit
 {:.no_toc}
@@ -202,7 +202,7 @@ This step is totally the same as for original [MAX integration](https://dash.app
 ##### Step 2: Create MaxMediationRewardedUtils
 {:.no_toc}
 
-The `MaxMediationRewardedUtils` is a helper class, which performs certain utilty work for the `MediationRewardedVideoAdUnit`, like passing the targeting keywords to the adapters.
+The `MaxMediationRewardedUtils` is a helper class, which performs certain utility work for the `MediationRewardedVideoAdUnit`, like passing the targeting keywords to the adapters.
 
 ##### Step 3: Create MediationRewardedVideoAdUnit
 {:.no_toc}
@@ -262,7 +262,7 @@ Prepare the `MaxNativeAdLoader` object before you make a bid request. It will be
 #### Step 2: Create and configure NativeAdUnit
 {:.no_toc}
 
-The `NativeAdUnit` class is responsible for making a bid request and providing a winning bid and targeting keywords. Fot the better targetting you should provide additional properties like `conteaxtType` and `placemantType`. 
+The `NativeAdUnit` class is responsible for making a bid request and providing a winning bid and targeting keywords. For better targeting you should provide additional properties like `contextType` and `placementType`.
 
 #### Step 3: Set up assets for bid request
 {:.no_toc}

prebid-mobile/modules/rendering/ios-sdk-integration-admob.md

@@ -105,7 +105,7 @@ This step is the same as for the original [AdMob integration](https://developers
 #### Step 2: Create AdMobMediationBannerUtils
 {:.no_toc}
 
-The `AdMobMediationBannerUtils` is a helper class, which performs certain utilty work for the `MediationBannerAdUnit`, such as passing the targeting keywords to the adapters and checking the visibility of the ad view.
+The `AdMobMediationBannerUtils` is a helper class, which performs certain utility work for the `MediationBannerAdUnit`, such as passing the targeting keywords to the adapters and checking the visibility of the ad view.
 
 #### Step 3: Create MediationBannerAdUnit
 {:.no_toc}
@@ -213,7 +213,7 @@ This step is the same as for the original [AdMob integration](https://developers
 #### Step 2: Create AdMobMediationInterstitialUtils
 {:.no_toc}
 
-The `AdMobMediationInterstitialUtils` is a helper class, which performs certain utilty work for the `MediationInterstitialAdUnit`, such as passing the targeting keywords to adapters and checking the visibility of the ad view.
+The `AdMobMediationInterstitialUtils` is a helper class, which performs certain utility work for the `MediationInterstitialAdUnit`, such as passing the targeting keywords to adapters and checking the visibility of the ad view.
 
 #### Step 3: Create MediationInterstitialAdUnit
 {:.no_toc}
@@ -328,7 +328,7 @@ This step is the same as for the original [AdMob integration](https://developers
 #### Step 2: Create MediationRewardedAdUnit
 {:.no_toc}
 
-The `AdMobMediationRewardedUtils` is a helper class, which performs certain utilty work for the `MediationRewardedAdUnit`, like passing the targeting keywords to the adapters.
+The `AdMobMediationRewardedUtils` is a helper class, which performs certain utility work for the `MediationRewardedAdUnit`, like passing the targeting keywords to the adapters.
 
 #### Step 3: Create MediationInterstitialAdUnit
 {:.no_toc}
@@ -442,12 +442,12 @@ Prepare the `Request` object before you make a bid request. It will be needed fo
 #### Step 2: Create AdMobMediationNativeUtils
 {:.no_toc}
 
-The `AdMobMediationNativeUtils` is a helper class, which performs certain utilty work for `MediationNativeAdUnit`, like passing the targeting keywords to adapters and checking the visibility of the ad view.
+The `AdMobMediationNativeUtils` is a helper class, which performs certain utility work for `MediationNativeAdUnit`, like passing the targeting keywords to adapters and checking the visibility of the ad view.
 
 #### Step 3: Create and configure MediationNativeAdUnit
 {:.no_toc}
 
-The `MediationNativeAdUnit` is part of the Prebid mediation API. This class is responsible for making a bid request and providing a winning bid and targeting keywords to the adapters. For better targetting you should provide additional properties like `conteaxtType` and `placemantType`.
+The `MediationNativeAdUnit` is part of the Prebid mediation API. This class is responsible for making a bid request and providing a winning bid and targeting keywords to the adapters. For better targeting you should provide additional properties like `contextType` and `placementType`.
 
 #### Step 4: Set up assets for bid request
 {:.no_toc}