remove redundant paragraph (#120)

## 💸 TL;DR
<!-- What's the three sentence summary of purpose of the PR -->
Removed redundant paragraph from question that read as two answers. The
What screen sizes should I design for? FAQ already covers responsive
design, UI Simulator testing, inline vs expanded behavior, and the same
reference links, so no extra content was added.

## ✅ Checks
<!-- Make sure your pr passes the CI checks and do check the following
fields as needed - -->
- [ ] CI tests (if present) are passing
- [ ] Adheres to code style for repo
- [ ] Contributor License Agreement (CLA) completed if not a Reddit
employee

Author: vdikransamarjian

docs/guides/faq.mdx

@@ -246,8 +246,6 @@ Use HTML launch entry points for all new and existing work. The older `splash` p
 
 Treat inline and expanded mode differently. Inline should avoid scroll traps and heavy gesture hijacking so users can still scroll past the post, while expanded is the right place for richer touch interaction and more space.
 
-There's no single canonical viewport size for all devices. Design responsively, test in [UI Simulator](./tools/ui_simulator.mdx), and use the current launch-mode docs for inline vs expanded behavior in [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md) and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md).
-
 </details>
 
 <span id="how-do-i-add-images-that-ship-with-my-app"></span>

versioned_docs/version-0.12/guides/faq.mdx

@@ -246,8 +246,6 @@ Use HTML launch entry points for all new and existing work. The older `splash` p
 
 Treat inline and expanded mode differently. Inline should avoid scroll traps and heavy gesture hijacking so users can still scroll past the post, while expanded is the right place for richer touch interaction and more space.
 
-There's no single canonical viewport size for all devices. Design responsively, test in [UI Simulator](./tools/ui_simulator.mdx), and use the current launch-mode docs for inline vs expanded behavior in [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md) and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md).
-
 </details>
 
 <span id="how-do-i-add-images-that-ship-with-my-app"></span>

versioned_docs/version-0.13/guides/faq.mdx

@@ -246,8 +246,6 @@ Use HTML launch entry points for all new and existing work. The older `splash` p
 
 Treat inline and expanded mode differently. Inline should avoid scroll traps and heavy gesture hijacking so users can still scroll past the post, while expanded is the right place for richer touch interaction and more space.
 
-There's no single canonical viewport size for all devices. Design responsively, test in [UI Simulator](./tools/ui_simulator.mdx), and use the current launch-mode docs for inline vs expanded behavior in [View modes and entry points](../capabilities/server/launch_screen_and_entry_points/view_modes_entry_points.md) and [Launch screen customization](../capabilities/server/launch_screen_and_entry_points/launch_screen_customization.md).
-
 </details>
 
 <span id="how-do-i-add-images-that-ship-with-my-app"></span>