Browser Monitoring Edits

[alai97]

What does this PR do?

Standardizes the naming of the "RUM Browser SDK" and small copy edits.

Motivation

#rum-docs Slack

Additional Notes

Remember to update the branch name in pull_config.yaml before merging!

---

Reviewer checklist

• Review the changed files.
• Review the URLs listed in the Preview section.
• Check images for PII
• Review any mentions of "Contact Datadog support" for internal support documentation.

[github-actions]

Preview links (active after the build_preview check completes):
https://docs-staging.datadoghq.com/alai97/rum-browser-naming-batch-update/real_user_monitoring/browser/collecting_browser_errors
https://docs-staging.datadoghq.com/alai97/rum-browser-naming-batch-update/real_user_monitoring/browser/modifying_data_and_context
https://docs-staging.datadoghq.com/alai97/rum-browser-naming-batch-update/real_user_monitoring/browser/monitoring_page_performance
https://docs-staging.datadoghq.com/alai97/rum-browser-naming-batch-update/real_user_monitoring/browser/monitoring_resource_performance
https://docs-staging.datadoghq.com/alai97/rum-browser-naming-batch-update/real_user_monitoring/browser/tracking_user_actions
https://docs-staging.datadoghq.com/alai97/rum-browser-naming-batch-update/real_user_monitoring/browser/troubleshooting

[BenoitZugmeyer]

🔨 warning: ‏‏If I understand correctly, changing this URL will pull the README from your branch instead of main. I think we should keep using main, so it updates when we make a change, WDYT?

[alai97]

Yes, this is just for the sake of the preview to connect the Browser Monitoring PR #1563 with!

[apigirl]

❗ Information So this is the pull_config_preview.yaml, the main site is pulled from the pull_config.yaml file. We've split them out to keep this problem from happening! So you should definitely return the branch to main, but even if it is merged in as-is, it won't be for production builds, just the preview sites. You should also always make sure to update both files with final changes.