round of 404 link fixes (#5661)

_includes/mobile/intro-bidding-only.md

@@ -90,7 +90,7 @@ The Ad Operations team will need to create line items in GAM. The creatives used
 | HTML banner, interstitial banner | hb_pb<br/>hb_format=banner | 3rd party HTML that loads the [PUC](/overview/prebid-universal-creative.html) | yes | [link](/adops/gam-creative-banner-sbs.html) |
 | Video (instream, non-instream, interstitial) | hb_pb<br/>hb_format=video<br/>inventoryType in (instream, mobile app) | VastUrl pointing to Prebid Cache | yes | [link](/adops/setting-up-prebid-video-in-dfp.html) |
 | Rewarded Video | hb_pb<br/>hb_format=video<br/>inventoryType in (instream, mobile app)<br/>rewarded adunits | VastUrl pointing to Prebid Cache | yes | [link](/adops/setting-up-prebid-video-in-dfp.html) |
-| In-app native | hb_pb<br/>hb_format=native | GAM native | no | [link](adops/gam-native.html#create-a-new-native-creative) |
+| In-app native | hb_pb<br/>hb_format=native | GAM native | no | [link](/adops/gam-native.html#create-a-new-native-creative) |
 | In-Webview native | hb_pb<br/>hb_format=native | 3rd party HTML that loads the native-trk script. | yes | [link](/adops/gam-native.html) |
 
 Notes:

_includes/mobile/intro-prebid-rendered.md

@@ -101,7 +101,7 @@ The AdOps team will need to create line items in GAM. The creatives used depend
 | HTML banner, interstitial banner or video, non-instream video | hb_pb<br/>hb_format=banner | 3rd party HTML that loads google_mobile_app_ads.js | no | [link](/adops/mobile-rendering-gam-line-item-setup.html#third-party-html) |
 | Instream Video | hb_pb<br/>hb_format=video<br/>inventoryType in (instream, mobile app) | VastUrl pointing to Prebid Cache | yes | [link](/adops/setting-up-prebid-video-in-dfp.html) |
 | Rewarded Video | hb_pb<br/>hb_format=video<br/>inventoryType in (instream, mobile app)<br/>rewarded adunits | VastUrl pointing to prebid-mobile-rewarded-vast.xml | no | [link](/adops/mobile-rendering-gam-line-item-setup.html#rewarded-video) |
-| In-app native | hb_pb<br/>hb_format=native | GAM native | no | [link](adops/gam-native.html#create-a-new-native-creative) |
+| In-app native | hb_pb<br/>hb_format=native | GAM native | no | [link](/adops/gam-native.html#create-a-new-native-creative) |
 
 Notes:
 

adops/creative-considerations.md

@@ -31,9 +31,9 @@ Here's a set of basic creative recommendations to use as a starting point:
 1. **Using Prebid Mobile?**
     1. Choose your integration method and see the "AdOps Guidance" section for that integration method.
         1. GAM Bidding-Only for [iOS](/prebid-mobile/pbm-api/ios/ios-sdk-integration-gam-original-api.html#ad-operations-guidance)/[Android](/prebid-mobile/pbm-api/android/android-sdk-integration-gam-original-api.html#ad-operations-guidance)
-        1. GAM Prebid-Rendered for [iOS](TBD)/[Android](TBD)
-        1. AdMob for [iOS](TBD)/[Android](TBD)
-        1. MAX for [iOS](TBD)/[Android](TBD)
+        1. GAM Prebid-Rendered for [iOS](/prebid-mobile/modules/rendering/ios-sdk-integration-gam.html)/[Android](/prebid-mobile/modules/rendering/android-sdk-integration-gam.html)
+        1. AdMob for [iOS](/prebid-mobile/modules/rendering/ios-sdk-integration-admob.html)/[Android](/prebid-mobile/modules/rendering/android-sdk-integration-admob.html)
+        1. MAX for [iOS](/prebid-mobile/modules/rendering/ios-sdk-integration-max.html)/[Android](/prebid-mobile/modules/rendering/android-sdk-integration-max.html)
 
 ## Types of Creatives
 

adops/gam-creative-banner-sbs.md

@@ -20,7 +20,7 @@ design tool, you'll need to follow the [GAM native](/adops/gam-native.html) page
 For complete instructions on setting up Prebid line items in Google Ad Manager, see [Google Ad Manager with Prebid Step by Step](/adops/step-by-step.html).
 
 {: .alert.alert-info :}
-Note that for Prebid Mobile, the In-Renderer video scenario is covered by video line items. See the [video creative reference](adops/setting-up-prebid-video-in-dfp.html) for details.
+Note that for Prebid Mobile, the In-Renderer video scenario is covered by video line items. See the [video creative reference](/adops/mobile-rendering-gam-line-item-setup.html) for details.
 
 ## Overview
 

adops/step-by-step.md

@@ -58,7 +58,7 @@ See [Key Values](/adops/key-values.html) for information on the keys you'll need
 
 Depending on your scenario, you will likely need several groups of line items.
 See the [line item essentials](/adops/line-item-creation.html) guide for details.
-How many line items are in each group depends on the [price granularity](/price-granularity.html).
+How many line items are in each group depends on the [price granularity](/adops/price-granularity.html).
 
 For instance, if you're running both Prebid.js and Prebid Mobile,
 you should consider having 2 sets of banner line items and 2 sets of video line items. If your banner line items are medium granularity (201 line items), and your

dev-docs/bidders/anyclip.md

@@ -25,7 +25,7 @@ sidebarType: 1
 
 ### Note
 
-For more information about [AnyClip](https://www.anyclip.com), please contact [[email protected]]([email protected]).
+For more information about [AnyClip](https://www.anyclip.com), please contact <[email protected]>.
 
 ### Bid Params
 

dev-docs/bidders/ix.md

@@ -413,7 +413,7 @@ Depending on the Prebid.js version that you are using, the steps to configure Pr
 
 **Configure Protected Audience API for Prebid.js versions 8.37.0 and up to 9.0.0**
 
-1. Build the `fledgeForGpt` module in your Prebid.js configuration by adding `fledgeForGpt` to the list of modules that you are already using. For more information about the module, see Prebid's [Protected Audience API (PAAPI) for GPT Module](/dev-docs/modules/fledgeForGpt.html) documentation.
+1. Build the `fledgeForGpt` module in your Prebid.js configuration by adding `fledgeForGpt` to the list of modules that you are already using. For more information about the module, see Prebid's [Protected Audience API (PAAPI) for GPT Module](/dev-docs/modules/paapiForGpt.html) documentation.
 2. Complete the following steps to make your ad units eligible for Protected Audience API demand: <br />
 **Note:** If you continue to use the `fledgeForGpt` property, you will receive a warning message in the console logs stating that the `fledgeForGpt` configuration options will soon be renamed to `paapi`. Therefore, Index recommends that you use the `paapi` property, which is available in Prebid.js version 8.37.0 or later.
     * In the `pbjs.setConfig().paapi` field, set the `defaultForSlots` parameter to `1`:
@@ -464,9 +464,9 @@ Depending on the Prebid.js version that you are using, the steps to configure Pr
 
 **Configure Protected Audience API for Prebid.js version 9.0.0 or later**
 
-1. Build the [PAAPI](/dev-docs/modules/paapi.html) module in your Prebid.js configuration by adding paapi to the list of modules that you are already using. For more information about the module, see Prebid's [Protected Audience API (PAAPI) for GPT Module(/dev-docs/modules/fledgeForGpt.html) documentation.
+1. Build the [PAAPI](/dev-docs/modules/paapi.html) module in your Prebid.js configuration by adding paapi to the list of modules that you are already using. For more information about the module, see Prebid's [Protected Audience API (PAAPI) for GPT Module(/dev-docs/modules/paapiForGpt.html) documentation.
 2. In the `pbjs.setConfig().paapi` field, set the `defaultForSlots` parameter to `1`. 
-3. In the `paapi.gpt.configWithTargeting` field, set `configWithTargeting` to `true`. For more control over configuring GPT slots to use PAAPI, set the `configWithTargeting` to `false` and use the `setPAAPIConfigForGPT` API. For more information about the configurations, see Prebid’s Prebid's [Protected Audience API (PAAPI) for GPT Module(/dev-docs/modules/fledgeForGpt.html) documentation. <br />The following code is an example of the `defaultForSlots` and `configWithTargeting` configuration:
+3. In the `paapi.gpt.configWithTargeting` field, set `configWithTargeting` to `true`. For more control over configuring GPT slots to use PAAPI, set the `configWithTargeting` to `false` and use the `setPAAPIConfigForGPT` API. For more information about the configurations, see Prebid’s Prebid's [Protected Audience API (PAAPI) for GPT Module(/dev-docs/modules/paapiForGpt.html) documentation. <br />The following code is an example of the `defaultForSlots` and `configWithTargeting` configuration:
 
   ```javascript
   pbjs.que.push(function() {

dev-docs/bidders/jwplayer.md

@@ -47,8 +47,8 @@ Instream and outstream video ads are supported.
 ## Modules to include in your build process
 
 You will need to include the `jwplayerBidAdapter` in your build. If you are building the JS binary on your own from source code, follow the instructions in [Prebid.js project README](https://github.com/prebid/Prebid.js/blob/master/README.md#build-optimization). 
-We recommend including the [jwplayerVideoProvider](dev-docs/modules/jwplayerVideoProvider.md) to connect Prebid.js to your JW Player instance via the [Prebid Video Module](prebid-video/video-module.md). 
-If you are not using the JW Player Video Provider, we suggest including the JW Player Real Time Data Provider [jwplayerRtdProvider](dev-docs/modules/jwplayerRtdProvider.md) in order to include JW Player's contextual ad targeting segments in your bid requests. 
+We recommend including the [jwplayerVideoProvider](/dev-docs/modules/jwplayerVideoProvider.html) to connect Prebid.js to your JW Player instance via the [Prebid Video Module](/dev-docs/modules/video.html). 
+If you are not using the JW Player Video Provider, we suggest including the JW Player Real Time Data Provider [jwplayerRtdProvider](/dev-docs/modules/jwplayerRtdProvider.html) in order to include JW Player's contextual ad targeting segments in your bid requests. 
 
 The following is an example build command that include these modules: <br />
 `gulp build --modules=jwplayerBidAdapter,jwplayerVideoProvider`<br />
@@ -96,7 +96,7 @@ You must include the following parameters at the bidder level, in `adUnit.bids[i
 
 ### mediaTypes.video
 
-We recommend populating as many params as possible in `adUnit.mediaTypes.video`. When using the [jwplayerVideoProvider](dev-docs/modules/jwplayerVideoProvider.md), these fields are populated automatically. 
+We recommend populating as many params as possible in `adUnit.mediaTypes.video`. When using the [jwplayerVideoProvider](/dev-docs/modules/jwplayerVideoProvider.html), these fields are populated automatically. 
 
 {: .table .table-bordered .table-striped }
 | Name               | Scope       | Type    | Description                                                                                                                                                                                                                                                                                                             |
@@ -109,7 +109,7 @@ We recommend populating as many params as possible in `adUnit.mediaTypes.video`.
 
 ### First Party Data (FPD)
 
-In release 4.30 and later, publishers who are not using the [jwplayerVideoProvider](dev-docs/modules/jwplayerVideoProvider.md) or [jwplayerRtdProvider](dev-docs/modules/jwplayerRtdProvider.md) can use the ortb2 method of setting First Party Data. 
+In release 4.30 and later, publishers who are not using the [jwplayerVideoProvider](/dev-docs/modules/jwplayerVideoProvider.html) or [jwplayerRtdProvider](/dev-docs/modules/jwplayerRtdProvider.html) can use the ortb2 method of setting First Party Data. 
 The following fields are required:
 
 {: .table .table-bordered .table-striped }

dev-docs/bidders/mediakeys.md

@@ -170,7 +170,6 @@ Mediakeys fully supports the following [Prebid.js Modules](https://docs.prebid.o
 | [Consent Management - US Privacy](https://docs.prebid.org/dev-docs/modules/consentManagementUsp.html) | Required in US - California |
 | [Supply Chain Object](https://docs.prebid.org/dev-docs/modules/schain.html)                           | Required for all traffic    |
 | [Instream Tracking](https://docs.prebid.org/dev-docs/modules/instreamTracking.html)                   | Required for Instream Video |
-| [First Party Data Enrichment](https://docs.prebid.org/dev-docs/modules/enrichmentFpdModule.html)      | Recommended for all traffic |
 
 Publishers must utilize the required modules in described scope to be able to receive bid responses.
 

dev-docs/bidders/ownadx.md

@@ -25,7 +25,7 @@ ortb_blocking_supported: false
 
 ### Note
 
-The OwnAdX Bidding adapter requires setup before beginning. Please contact us at [[email protected]]([email protected])
+The OwnAdX Bidding adapter requires setup before beginning. Please contact us at <[email protected]>.
 
 ### Bid Params
 

dev-docs/modules/adagioRtdProvider.md

@@ -15,10 +15,10 @@ sidebarType : 1
 
 ## Overview
 
-This module can be used in combination with [Adagio Bid Adapter](/dev-docs/bidders/adagioBidAdapter.md) (SSP) and/or with Adagio prebid server endpoint.
+This module can be used in combination with [Adagio Bid Adapter](/dev-docs/bidders/adagio.html) (SSP) and/or with Adagio prebid server endpoint.
 It computes and collects data required to leverage Adagio viewability and attention prediction engine.
 
-Please contact [[email protected]]([email protected]) for more information.
+Please contact <[email protected]> for more information.
 
 {% include dev-docs/loads-external-javascript.md %}
 

dev-docs/modules/dfpAdpod.md

@@ -14,7 +14,7 @@ sidebarType : 1
 
 {:.no_toc}
 
-This module exposes the [`pbjs.adServers.dfp.buildAdpodVideoUrl](/dev-docs/publisher-api-reference/adServers.dfp.buildAdpodVideoUrl.html) method, required to use [adpod](/dev-docs/modules/adpod.md) with Google Ad Manager.
+This module exposes the [`pbjs.adServers.dfp.buildAdpodVideoUrl](/dev-docs/publisher-api-reference/adServers.dfp.buildAdpodVideoUrl.html) method, required to use [adpod](/dev-docs/modules/adpod.html) with Google Ad Manager.
 
 ## Further Reading
 

dev-docs/modules/paapiForGpt.md

@@ -59,7 +59,7 @@ pbjs.requestBids({
 
 It's important to invoke the `pbjs.setPAAPIConfigForGPT()` function within the `bidsBackHandler` whenever new bids are requested, such as when refreshing ad slots. This ensures that the auctionConfig is manually applied to a GPT slot when autoconfig is disabled. Without this manual configuration, GPT slots will not be properly set up to handle new bids, potentially resulting in duplicate impression calls.
 
-See the [API reference](/dev-docs/publisher-api-reference/setPAAPIConfigForGpt.html) for more options.
+See the [API reference](/dev-docs/publisher-api-reference/setPAAPIConfigForGPT.html) for more options.
 
 ## Related Reading
 

dev-docs/modules/validationFpdModule.md

@@ -65,5 +65,4 @@ and if it exists, certain fields will be removed.
 # Related Reading
 
 - [Prebid.js First Party Data feature](/features/firstPartyData.html)
-- [First Party Data Enrichment Module](/dev-docs/modules/enrichmentFpdModule)
 - [OpenRTB 2.5](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf)

examples/video/index.md

@@ -25,11 +25,8 @@ The following examples are available:
 
 ## Instream
 
-- [Brightcove](/examples/video/instream/brightcove/pb-ve-brightcove.html)
-- [Flowplayer](/examples/video/instream/flowplayer/pb-ve-flowplayer.html)
 - [JW Player](/examples/video/instream/jwplayer/pb-ve-jwplayer-platform.html)
 - [JW Player (Self-Hosted)](/examples/video/instream/jwplayer/pb-ve-jwplayer-hosted.html)
-- [Kaltura](/examples/video/instream/kaltura/pb-ve-kaltura.html)
 - [VideoJS](/examples/video/instream/videojs/pb-ve-videojs.html)
 
 ## Instream and Banner Mixed Page

features/timeouts-video.md

@@ -11,7 +11,7 @@ sidebarType: 1
 
 Further Content:
 
-- [Prebid.js Timeouts](/features/timeout.html)
+- [Prebid.js Timeouts](/features/timeouts.html)
 - [All videos](/overview/all-videos.html)
 
 Related Videos

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

@@ -205,7 +205,7 @@ GAM setup:
 
 1. Leave the original order and ad units as is. They are not relevant for the rendering approach but they will serve ads for released applications.
 2. Create a new GAM ad unit.
-3. Setup a new [GAM Order](rendering-gam-line-item-setup.html) for rendering approach. 
+3. Setup a new [GAM Order](/adops/mobile-rendering-gam-line-item-setup.html) for rendering approach. 
 
 Integration:
 
@@ -299,7 +299,7 @@ GAM setup:
 
 1. Leave the original order and ad units as is. They are not relevant for the rendering approach but they will serve ads for released applications.
 2. Create a new GAM ad unit.
-3. Setup a new [GAM Order](rendering-gam-line-item-setup.html) for rendering approach.
+3. Setup a new [GAM Order](/adops/mobile-rendering-gam-line-item-setup.html) for rendering approach.
 
 Integration:
 

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

@@ -196,7 +196,7 @@ GAM setup:
 
 1. Leave the original order and ad units as is. They are not relevant for the rendering approach but they will serve ads for released applications.
 2. Create a new GAM ad unit.
-3. Setup the new [GAM Order](prebid-mobile/modules/rendering/ios-sdk-integration-gam.html) for rendering approach.
+3. Setup the new [GAM Order](/prebid-mobile/modules/rendering/ios-sdk-integration-gam.html) for rendering approach.
 
 Integration:
 
@@ -285,7 +285,7 @@ GAM setup:
 
 1. Leave the original order and ad units as is. They are not relevant for the rendering approach but they will serve ads for released applications.
 2. Create a new GAM ad unit.
-3. Setup the new [GAM Order](prebid-mobile/modules/rendering/ios-sdk-integration-gam.html) for rendering approach.
+3. Setup the new [GAM Order](/prebid-mobile/modules/rendering/ios-sdk-integration-gam.html) for rendering approach.
 
 Integration:
 

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

@@ -196,7 +196,7 @@ There are several types of parameters app developers should consider providing t
 - First Party Data to help bidders understand the context and/or u
 ser better.
 
-See the [global parameters page](/prebid-mobile/pbm-api/android/pbm-targeting-params-android.html) for details.
+See the [global parameters page](/prebid-mobile/pbm-api/android/pbm-targeting-android.html) for details.
 
 ## Supported Android versions