diff --git a/dev-docs/bidders/beachfront.md b/dev-docs/bidders/beachfront.md
index fc12fab12f..cedf83c05d 100644
--- a/dev-docs/bidders/beachfront.md
+++ b/dev-docs/bidders/beachfront.md
@@ -1,7 +1,7 @@
 ---
 layout: bidder
 title: Beachfront
-description: Prebid Beachfront Bidder Adaptor
+description: Prebid Beachfront Bidder Adapter
 biddercode: beachfront
 media_types: video
 gdpr_supported: true
@@ -10,6 +10,7 @@ userIds: unifiedId, identityLink
 prebid_member: true
 pbjs: true
 pbs: true
+pbs_app_supported: true
 ---
 
 ### Registration
@@ -74,8 +75,13 @@ For further information, please contact adops@beachfront.com.
 
 ### Prebid Server
 
-As seen in the JSON response from \{your PBS server\}\/bidder\/params [(example)](https://prebid.adnxs.com/pbs/v1/bidders/params), the beachfront bidder can take either an "appId" parameter, or an "appIds" parameter. If the request is for one media type, the appId parameter should be used with the value of the Exchange Id on the Beachfront platform.
+As seen in the JSON response from \{your PBS server\}\/bidder\/params [(example)](https://prebid.adnxs.com/pbs/v1/bidders/params), the beachfront
+bidder can take either an "appId" parameter, or an "appIds" parameter. If the request is for one media type, the appId parameter should be used
+with the value of the Exchange Id on the Beachfront platform.
 
-The appIds parameter is for requesting a mix of banner and video. It has two parameters, "banner", and "video" for the appIds of two appropriately configured exchanges on the platform. The appIds parameter can be sent with just one of its two parameters and it will behave like the appId parameter.
+The appIds parameter is for requesting a mix of banner and video. It has two parameters, "banner", and "video" for the appIds of two appropriately
+configured exchanges on the platform. The appIds parameter can be sent with just one of its two parameters and it will behave like the appId parameter.
 
-If the request includes an appId configured for a video response, the videoResponseType parameter can be defined as "nurl", "adm" or "both". These will apply to all video returned. If it is not defined, the response type will be a nurl. The definitions for "nurl" vs. "adm" are here: (https://github.com/mxmCherry/openrtb/blob/master/openrtb2/bid.go).
+If the request includes an appId configured for a video response, the videoResponseType parameter can be defined as "nurl", "adm" or "both".
+These will apply to all video returned. If it is not defined, the response type will be a nurl. The definitions for "nurl" vs. "adm" are
+here: (https://github.com/mxmCherry/openrtb/blob/master/openrtb2/bid.go).