docs: fix various typos demonstration of robot pr

dev-docs/activity-controls.md

@@ -235,7 +235,7 @@ If `allow` is not defined, the rule is assumed to assert **true** (i.e. allow th
 
 #### Always include a particular bidder in auctions
 
-This is similiar to the 'vendor exception' feature of the [TCF Control Module](/dev-docs/modules/tcfControl.html). This would always allow bidderA to participate in the auction, even without explicit consent in GDPR scenarios. It might indicate, for instance, that this is a 'first party bidder'.
+This is similar to the 'vendor exception' feature of the [TCF Control Module](/dev-docs/modules/tcfControl.html). This would always allow bidderA to participate in the auction, even without explicit consent in GDPR scenarios. It might indicate, for instance, that this is a 'first party bidder'.
 
 ```javascript
 pbjs.setConfig({

dev-docs/bidder-adaptor.md

@@ -650,7 +650,7 @@ Sample data received by this function:
 
 The `onBidBillable` function will be called when it deems a bid to be billable. When a bid wins, it is by default also billable. That is, by default, onBidWon and onBidBillable will be called one after the other. However, a publisher can flag adUnits as being separately billable: `pbjs.addAdUnits({deferBilling: true, ...})`. Winning bids for adUnits with `deferBilling` set to true, trigger the onBidWon function but not the onBidBillable function. When appropriate (e.g. an interstitial is displayed), the publisher may then call the public API method, `pbjs.triggerBilling(winningBidObjectToBill)` passing the winning bid to be billed, which will trigger onBidBillable.
 
-Sample data received by this function (same as what is recieved for onBidWon):
+Sample data received by this function (same as what is received for onBidWon):
 
 ```javascript
 {
@@ -814,7 +814,7 @@ If your adapter supports banner and video media types, make sure to include `'ba
 
 ### Step 2: Accept video parameters and pass them to your server
 
-Video parameters are often passed in from the ad unit in a `video` object. As of Prebid 4.0 the following paramters should be read from the ad unit when available; bidders can accept overrides of the ad unit on their bidder configuration parameters but should read from the ad unit configuration when their bidder parameters are not set. Parameters one should expect on the ad unit include:
+Video parameters are often passed in from the ad unit in a `video` object. As of Prebid 4.0 the following parameters should be read from the ad unit when available; bidders can accept overrides of the ad unit on their bidder configuration parameters but should read from the ad unit configuration when their bidder parameters are not set. Parameters one should expect on the ad unit include:
 
 * mimes
 * minduration

dev-docs/bidders/smartx.md

@@ -65,6 +65,6 @@ This adapter requires setup and approval from the smartclip team. Please contact
 | `title`         | optional | The player can show a freely definable text, a macro `[remainingTime]` in this string will be replaced with the remaining play time of the ad in seconds. | `'Advertisement [remainingTime]s'` | `string`    |
 | `skipOffset`    | optional | In order to enable skipping from the start set the delay to `0`, to show the skip button after 5 seconds set it to `5`. Setting a general skipOffset is discouraged. Note that linear creatives carrying a skipsoffet attribute will override the general player setting. By default the player does not set a general skipoffset, so a skip button will only be shown, if an ad has a specific skipoffset attached. |  `0`  | `integer`   |
 | `startOpen`     | optional | Per default the player will start fully expanded, if a valid ad can be played. Setting this option to `false` will trigger an expand animation instead once the player comes into view. Default is `true`.              | `'false'`        | `string`    |
-| `endingScreen`  | optional | By default the player will not close, but show the ending screen when an advertisement is complete (last frame of the ad and a replay button, if an advertisment comes with an endcard that will be shown). If set to `false` the player will collapse. Some VPAID creatives can cause issues with ending screen or replay behaviour. Default is `true`.              | `'true'`         | `string`    |
+| `endingScreen`  | optional | By default the player will not close, but show the ending screen when an advertisement is complete (last frame of the ad and a replay button, if an advertisement comes with an endcard that will be shown). If set to `false` the player will collapse. Some VPAID creatives can cause issues with ending screen or replay behaviour. Default is `true`.              | `'true'`         | `string`    |
 | `desiredBitrate`| optional | You can specify a target bitrate for the creative, higher values will increase video quality but will cost bandwidth. Value is given in kpbs. Default is `700`.                       | `800`            | `integer`   |
-| `visibilityThreshold`| optional | Defines the percentage of the player which has to be in the visible area to play and pause the advertisment. The default is `50`.                           | `50`             | `integer`   |
+| `visibilityThreshold`| optional | Defines the percentage of the player which has to be in the visible area to play and pause the advertisement. The default is `50`.                           | `50`             | `integer`   |

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

@@ -315,7 +315,7 @@ Prepare the `AdLoader` and `AdRequest` objects before you make the bid request.
 #### Step 2: Create NativeAdUnit
 {:.no_toc}
 
-The `NativeAdUnit` is responsible for making bid requests. Once the bid responce is received you can load an ad from AdMob.
+The `NativeAdUnit` is responsible for making bid requests. Once the bid response is received you can load an ad from AdMob.
 
 #### Step 3: Configure NativeAdUnit
 {:.no_toc}

prebid-mobile/pbm-api/android/pbm-targeting-android.md

@@ -447,9 +447,9 @@ Since version 2.0.6, Prebid SDK reads and sends GPP signals:
 ## Open Measurement SDK (OMSDK) API
 
 {: .alert.alert-info :}
-Defining OMSDK values is only relevant for the 'Bidding-Only' Prebid integration with GAM. In this case the creative is rendered by GMA SDK and publishers should provide OMID description in the bid request. If you use Prebid SDK as a rendering engine you shouldn’t use these properties -- it sends them automaticaly according to the current OMID setup.
+Defining OMSDK values is only relevant for the 'Bidding-Only' Prebid integration with GAM. In this case the creative is rendered by GMA SDK and publishers should provide OMID description in the bid request. If you use Prebid SDK as a rendering engine you shouldn’t use these properties -- it sends them automatically according to the current OMID setup.
 
-OMSDK is designed to facilitate 3rd party viewability and verification measurement for ads served in mobile app enviroments. Prebid SDK will provide the signaling component to Bid Adapters by way of Prebid Server, indicating that the impression is eligible for OMSDK support. Prebid SDK does not currently integrate with OMSDK itself, instead it will rely on a publisher ad server to render viewability and verification measurement code.
+OMSDK is designed to facilitate 3rd party viewability and verification measurement for ads served in mobile app environments. Prebid SDK will provide the signaling component to Bid Adapters by way of Prebid Server, indicating that the impression is eligible for OMSDK support. Prebid SDK does not currently integrate with OMSDK itself, instead it will rely on a publisher ad server to render viewability and verification measurement code.
 
 There are three components to signaling support for OMSDK:
 

prebid-mobile/pbm-api/ios/code-integration-ios.md

@@ -392,7 +392,7 @@ Prebid.shared.logLevel = .verbose
 // Set Prebid timeout in milliseconds
 Prebid.shared.timeoutMillis = 3000
 
-// Enable Prebid Server debug respones
+// Enable Prebid Server debug responses
 Prebid.shared.pbsDebug = true
 
 // Stored responses  can be one of storedAuction response or storedBidResponse

prebid-mobile/pbm-api/ios/pbm-targeting-ios.md

@@ -318,9 +318,9 @@ Since version 2.0.6, Prebid SDK reads and sends GPP signals:
 ## Open Measurement SDK (OMSDK) API
 
 {: .alert.alert-info :}
-Defining OMSDK values is only relevant for the 'Bidding-Only' Prebid integration with GAM. In this case the creative is rendered by GMA SDK and publishers should provide OMID description in the bid request. If you use Prebid SDK as a rendering engine you shouldn’t use these properties -- it sends them automaticaly according to the current OMID setup.
+Defining OMSDK values is only relevant for the 'Bidding-Only' Prebid integration with GAM. In this case the creative is rendered by GMA SDK and publishers should provide OMID description in the bid request. If you use Prebid SDK as a rendering engine you shouldn’t use these properties -- it sends them automatically according to the current OMID setup.
 
-OMSDK is designed to facilitate 3rd party viewability and verification measurement for ads served in mobile app enviroments. Prebid SDK will provide the signaling component to Bid Adapters by way of Prebid Server, indicating that the impression is eligible for OMSDK support. Prebid SDK does not currently integrate with OMSDK itself, instead it will rely on a publisher ad server to render viewability and verification measurement code.
+OMSDK is designed to facilitate 3rd party viewability and verification measurement for ads served in mobile app environments. Prebid SDK will provide the signaling component to Bid Adapters by way of Prebid Server, indicating that the impression is eligible for OMSDK support. Prebid SDK does not currently integrate with OMSDK itself, instead it will rely on a publisher ad server to render viewability and verification measurement code.
 
 There are three components to signaling support for OMSDK:
 

prebid-mobile/pbm-api/ios/pbm-util-ios.md

@@ -31,7 +31,7 @@ func bannerViewDidReceiveAd(_ bannerView: GoogleMobileAds.BannerView) {
         // In the case of Prebid's line item - resize te ad view
         bannerView.resize(adSizeFor(cgSize: size))
     }, failure: { (error) in
-        PrebidDemoLogger.shared.error("Error occuring during searching for Prebid creative size: \(error)")
+        PrebidDemoLogger.shared.error("Error occurring during searching for Prebid creative size: \(error)")
     })
 }
 {% endcapture %}
@@ -44,7 +44,7 @@ func bannerViewDidReceiveAd(_ bannerView: GoogleMobileAds.BannerView) {
         // In the case of Prebid's line item - resize te ad view
         bannerView.resize(GADAdSizeFromCGSize(size))
     }, failure: { (error) in
-        PrebidDemoLogger.shared.error("Error occuring during searching for Prebid creative size: \(error)")
+        PrebidDemoLogger.shared.error("Error occurring during searching for Prebid creative size: \(error)")
     })
 }
 {% endcapture %}

prebid-mobile/recipes/subrecipes/android/gam-bidding-only-multiformat.md

@@ -98,7 +98,7 @@ private fun createNativeParameters(): NativeParameters {
 }
 ```
 
-If you use Custom Native Ads follow the [guide](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/native-banner) on how to implement processing of the ad response of the respective type. The following code snipet demonstrates how you can process the banner, video and in-banner native (Native Styles) ad resposnse:
+If you use Custom Native Ads follow the [guide](https://developers.google.com/ad-manager/mobile-ads-sdk/ios/native-banner) on how to implement processing of the ad response of the respective type. The following code snippet demonstrates how you can process the banner, video and in-banner native (Native Styles) ad response:
 
 ``` kotlin
 private fun loadGam(gamRequest: AdManagerAdRequest) {

prebid-mobile/recipes/subrecipes/ios/gam-bidding-only-html-banner.md

@@ -85,7 +85,7 @@ In case you use a single-size banner (e.g., 300x250), you don't need to make a c
         guard let bannerView = bannerView as? AdManagerBannerView else { return }
         bannerView.resize(adSizeFor(cgSize: size))
     }, failure: { (error) in
-        PrebidDemoLogger.shared.error("Error occuring during searching for Prebid creative size: \(error)")
+        PrebidDemoLogger.shared.error("Error occurring during searching for Prebid creative size: \(error)")
     })
 }
 {% endcapture %}

prebid-mobile/recipes/subrecipes/ios/gam-bidding-only-multiformat.md

@@ -118,7 +118,7 @@ To handle the banner, video and in-banner native (Native Styles) ads:
         self?.bannerView.constraints.first { $0.firstAttribute == .width }?.constant = size.width
         self?.bannerView.constraints.first { $0.firstAttribute == .height }?.constant = size.height
     }, failure: { (error) in
-        PrebidDemoLogger.shared.error("Error occuring during searching for Prebid creative size: \(error)")
+        PrebidDemoLogger.shared.error("Error occurring during searching for Prebid creative size: \(error)")
     })
 }
 {% endcapture %}
@@ -134,7 +134,7 @@ To handle the banner, video and in-banner native (Native Styles) ads:
         self?.bannerView.constraints.first { $0.firstAttribute == .width }?.constant = size.width
         self?.bannerView.constraints.first { $0.firstAttribute == .height }?.constant = size.height
     }, failure: { (error) in
-        PrebidDemoLogger.shared.error("Error occuring during searching for Prebid creative size: \(error)")
+        PrebidDemoLogger.shared.error("Error occurring during searching for Prebid creative size: \(error)")
     })
 }
 {% endcapture %}

prebid-server/endpoints/openrtb2/pbs-endpoint-auction.md

@@ -1414,7 +1414,7 @@ For example, this request:
           },
           "storedbidresponse": [
             { "bidder": "BidderA", "id": "5555555", "replaceimpid":true }
-            // note: no storedbidrespose for bidderB
+            // note: no storedbidresponse for bidderB
           ]
         }
       }

prebid-server/endpoints/openrtb2/pbs-endpoint-video.md

@@ -25,7 +25,7 @@ The process is similar to [Prebid.js client side](/prebid-video/video-long-form.
 1. Application makes request for a video stream.
 2. An SSAI Server sends a video request to PBS, specifying the pod requirements.
 3. PBS sends a request for bids to selected demand partners by relaying OpenRTB requests to them.
-4. Demand partners return a bid response to PBS. If competitive seperation is enabled, PBS peforms [category translation](/dev-docs/modules/categoryTranslation.html) on each bid. Whether category translation is required or not, the bids are stored in prebid cache.
+4. Demand partners return a bid response to PBS. If competitive separation is enabled, PBS performs [category translation](/dev-docs/modules/categoryTranslation.html) on each bid. Whether category translation is required or not, the bids are stored in prebid cache.
 5. PBS generates key-value pairs that are comprised of price, category, and duration values. The key is `hb_pb_cat_dur` and each component of the key name after the `hb` represents a related value.  
     
       `_pb` represents the price bucket.

prebid-server/features/pbs-default-request.md

@@ -6,14 +6,14 @@
 
 # Server Based Global Default Request
 
-This allows a defaut stored request to be defined that allows the server to set up some defaults for all incoming requests. A request specified stored request will override these defaults, and of course any options specified directly in the stored request override both. The default stored request is only read on server startup, it is meant as an installation static default rather than a dynamic tuning option.
+This allows a default stored request to be defined that allows the server to set up some defaults for all incoming requests. A request specified stored request will override these defaults, and of course any options specified directly in the stored request override both. The default stored request is only read on server startup, it is meant as an installation static default rather than a dynamic tuning option.
 
 A common use case is to "hard code" aliases into the server. This saves having to specify them on all incoming requests, and/or on all stored requests. To help support automation and alias discovery we can flag that any aliases found in the file be added to the bidder info endpoints.
 
 ## Config Options
 
 In PBS-Go, there are several config options are exposed to support this feature.
 ```
 default_request:
     type: "file"
     file:
@@ -24,15 +24,15 @@
 The `file.name` option is the path/filename of a JSON file containing default request JSON. See the [stored request doc](/prebid-server/features/pbs-storedreqs.html) and the [openrtb2/auction endpoint doc](/prebid-server/endpoints/openrtb2/pbs-endpoint-auction.html) for details about the syntax.
 
 PBS-Java has a slightly different configuration in application.yaml:
 ```
 default-request:
     file:
         path: "/path/to/default.json"
 ```
 
 
 For both PBS-Go and PBS-Java, here's an example default request file:
 ```
 {
     "tmax": "500",
     "regs": {
@@ -48,7 +48,7 @@
         }
     }
 }
 ```
 This JSON is merged into the incoming requests at the top level. The values can be overridden by both Stored Requests _and_ the incoming HTTP request payload.
 
 The `info` option (PBS-Go only) determines if the aliased bidders will be exposed on the `/info` endpoints. If true the alias name will be added to the list returned by

prebid-server/use-cases/pbs-lfv.md

@@ -22,7 +22,7 @@
 1. Application makes request for a video stream.
 2. An SSAI Server sends a video request to PBS, specifying the pod requirements.
 3. PBS sends a request for bids to selected demand partners by relaying OpenRTB requests to them.
-4. Demand partners return a bid response to PBS. If competitive seperation is enabled, PBS peforms [category translation](/dev-docs/modules/categoryTranslation.html) on each bid. Whether category translation is required or not, the bids are stored in prebid cache.
+4. Demand partners return a bid response to PBS. If competitive separation is enabled, PBS performs [category translation](/dev-docs/modules/categoryTranslation.html) on each bid. Whether category translation is required or not, the bids are stored in prebid cache.
 5. PBS generates key-value pairs that are comprised of price, category, and duration values.
 6. The SSAI server parses the returned key-values, appending them as a query string to the ad server request URL and submits the request.
 7. The ad server returns the optimized pod.
@@ -31,4 +31,4 @@
 10. The stitched stream is returned to the application.
 
 ## Further Reading
 - [Long Form Video Endpoint](/prebid-server/endpoints/openrtb2/pbs-endpoint-video.html)