Tweaks to intro to primitives page (#731)

Closes #646 

Remove distracting formatting and review use of the word "provider" on
this page.

---------

Co-authored-by: Frank Harkins <frankharkins@hotmail.co.uk>

docs/run/primitives.mdx

@@ -6,15 +6,15 @@ description: Introduction to primitives in Qiskit and Qiskit Runtime, and an exp
 
 # Introduction to primitives
 
-Computing systems are built upon multiple layers of **abstraction**. Abstractions allow to focus on a
+Computing systems are built upon multiple layers of abstraction. Abstractions allow us to focus on a
 particular level of detail relevant to the task at hand. The closer you get to the hardware,
 the lower the level of abstraction you'll need (for example, you could
 want to manipulate electrical signals), and vice versa, the more complex the task you want to perform,
 the higher-level the abstractions will be (for example, you could be using a programming library to perform
 algebraic calculations).
 
-In this context, a **primitive** is the smallest processing instruction, the simplest building block from which
-one can create something **useful** for a given **abstraction** level.
+In this context, a primitive is the smallest processing instruction, the simplest building block from which
+one can create something useful for a given abstraction level.
 
 The recent progress in quantum computing has increased the need to work at higher levels of abstraction.
 As we move towards larger systems and more complex workflows, the focus shifts from interacting with individual