Update to include info on how to get to RUM sessions

content/en/tracing/services/resource_page.md

@@ -78,9 +78,9 @@ Datadog provides you visibility into how a web resource impacts your frontend ap
 
 {{< img src="tracing/visualization/resource/resource_frontend_impact.png" alt="A table showing several key metrics for a list of views sending requests to a particular resource" style="width:100%;" >}} 
 
-You can isolate requests and errors over time for a specific frontend view by hovering over a RUM View Name in the table and clicking on "Isolate this View". You can also explore the sampled traces that include the resource to frontend views by clicking on "View Traces" at the top right of the panel or clicking on the context menu for a specific frontend view in the table. 
+Isolate requests and errors over time for a specific frontend view by hovering over a RUM View Name in the table and clicking on "Isolate this View". From here, you can explore sampled traces originating from the frontend views by clicking on "View Traces" at the top right of the panel. You can also investigate the sampled RUM sessions for each view by clicking on the context menu for a frontend view in the table. 
 
-The frontend impact panel is only available if 1) you use Real User Monitoring (RUM) and 2) the resource belongs to a web service. Unlike the requests, errors, and latency graphs which use unsampled data sources, the frontend impact metrics are built on sampled trace data from the past 1 hour: 
+The frontend impact panel is only available if you use Real User Monitoring (RUM) and the resource belongs to a web service. Unlike the requests, errors, and latency graphs which use unsampled data sources, the frontend impact metrics are built on sampled trace data from the past 1 hour: 
 
 `RUM View Name:` 
 : Name of the frontend view 
@@ -100,8 +100,6 @@ The frontend impact panel is only available if 1) you use Real User Monitoring (
 `Requests` 
 : Number of requests originating from the frontend view  
 
-
-
 
 ## Span summary