fix performance headings to match tab names (#4494)

* fixed headings to match tab names

* moved widgets image up on the page

* Update src/docs/product/performance/filters-display.mdx

* Update src/docs/product/performance/filters-display.mdx

Author: imatwawana

src/docs/product/performance/filters-display.mdx

@@ -10,27 +10,27 @@ You can filter the information displayed on the **Performance** page by searchin
 
 ## Transaction and Trend Views
 
-The page default is to view transactions, but you can use the “By Transaction/By Trend” toggle to change the overall display of the page. The different ways you can filter and set the display of transactions is described fully on this page. To learn more about viewing transactions by trend, see our [Trends View documentation](/product/performance/trends/).
+The page displays a view of transactions, but you can click the “View Trends” button to view trends information. The different ways you can filter and set the display of transactions is described fully on this page. To learn more about viewing transactions by trend, see our [Trends View documentation](/product/performance/trends/).
 
 ## Tabs {#display-filter}
 
-Each tab in **Performance** displays an automatically selected set of [widgets](#widgets) and table columns based on the platform of your project. For example, a JavaScript project defaults to a Frontend (Pageload) display. Each tab and its [metrics](/product/performance/metrics/) are explained below.
+Each tab in **Performance** displays an automatically selected set of [widgets](#widgets) and table columns based on the platform of your project. For example, a JavaScript project displays the "Web Vitals" tab by default. Each tab and its [metrics](/product/performance/metrics/) are explained below.
 
 ### All Transactions
 
 When you select "All Transactions", the table includes all frontend and backend transactions.
 
 <!-- ![Performance Homepage with Display: All](00_performance_landing.png) -->
 
-### Frontend (Pageload)
+### Web Vitals {#frontend-pageload}
 
-"Frontend (Pageload)" puts an emphasis on [Web Vitals](/product/performance/web-vitals/). The transactions are automatically filtered to only include `transaction.op:pageload`. This generally corresponds to all browser page transitions that are not handled internally in SPA frameworks, such as React or Vue.
+[Web Vitals](/product/performance/web-vitals/) includes frontend pageload transactions. The transactions are automatically filtered to only include `transaction.op:pageload`. This generally corresponds to all browser page transitions that are not handled internally in SPA frameworks, such as React or Vue.
 
 ![Performance Frontend(Pageload) tab](performance-landing-widgets.png)
 
-### Frontend (Other)
+### Frontend {#frontend-other}
 
-"Frontend (Other)" includes any other frontend transaction that is not a pageload. The filter `transaction.op:!pageload` automatically gets added. This generally corresponds to page transitions handled internally in SPA frameworks, such as React or Vue. Note that if you've selected a backend project, this mode also displays backend transactions.
+"Frontend" includes any other frontend transaction that is not a pageload. The filter `transaction.op:!pageload` automatically gets added. This generally corresponds to page transitions handled internally in SPA frameworks, such as React or Vue. Note that if you've selected a backend project, this mode also displays backend transactions.
 
 ### Backend
 
@@ -61,10 +61,12 @@ You can compare graphs side by side to find any relevant correlations. For examp
 
 ## Widgets
 
-Widgets offer visualizations that you can change to best match your workflow. In the first row, there are time series and distribution graphs of common metrics for the selected project type (frontend or backend), such as User Misery or Failure Rate. You can compare these side-by-side to find any correlations.
+Widgets offer visualizations that you can change to best match your workflow.
 
 ![Performance Homepage with Widgets](performance-landing-widgets.png)
 
+In the first row, there are time series and distribution graphs of common metrics for the selected project type (frontend or backend), such as User Misery or Failure Rate. You can compare these side-by-side to find any correlations.
+
 In the second row, there are actionable widgets that can show you areas of concern in your application, such as Most Related Errors or Most Recurring Issues. Below these widgets, there are links to other parts of the application, which you can follow to see additional context.
 
 Each widget has a menu in the top right where can you change the widget shown. Your changes will be persisted locally either for the session or until application storage is cleared. After that, the default set of widgets is displayed.