Fix 2 typos

Author: Alex Krawiec

docs/pricing/quotas/manage-ui-profile-hours.mdx

@@ -34,11 +34,11 @@ UI Profiling provides two "lifecycle" modes that can be used to control when the
 
 ### On Mobile
 
-To estimate monthly usage for UI profiling when used on mobile, the calculation is **average user session length in hours * the number of sampled user sessions per month.** For example, if the average user session length is 6 minutes and there are 10,000 sampled user sessions per month, then the total usage os **0.1 hours * 10,000 sessions = 1,000 hours per month.** You can reduce the number of profiling hours by profiling a smaller number of user sessions (reducing profile_session_sample_rate), or only profiling devices or configurations tht are particularly performance sensitive (like low-end mobile devices).
+To estimate monthly usage for UI profiling when used on mobile, the calculation is **average user session length in hours * the number of sampled user sessions per month.** For example, if the average user session length is 6 minutes and there are 10,000 sampled user sessions per month, then the total usage os **0.1 hours * 10,000 sessions = 1,000 hours per month.** You can reduce the number of profiling hours by profiling a smaller number of user sessions (reducing `profile_session_sample_rate`), or only profiling devices or configurations tht are particularly performance sensitive (like low-end mobile devices).
 
 ### In The Browser
 
-To estimate monthly usage for UI Profiling when used in the browser, the calculation is **average user session length in hours * the number of user sessions per month.** FOr example, if the average user session length is 6 minutes and there are 10,000 sampled user sessions per month, then the total usage is **0.1 hours * 10,000 sessions = 1,000 hours per month**. You can reduce the cost of profiling by profiling a smaller number of user sessions (reducing `profile_session_sample_rate`).                                                                         
+To estimate monthly usage for UI Profiling in the browser, the calculation is **average user session length in hours * the number of user sessions per month.** For example, if the average user session length is 6 minutes and there are 10,000 sampled user sessions per month, then the total usage is **0.1 hours * 10,000 sessions = 1,000 hours per month**. You can reduce the number of profiling hours by profiling a smaller number of user sessions (reducing `profile_session_sample_rate`).                                                                         
 
 ## How Do You Purchase UI Profiling?