A few markdown formatting fixes and spelling

Signed-off-by: steve lasker <[email protected]>

draft-salowey-wimse-arch.md

@@ -31,13 +31,10 @@ author:
     organization:
     email: [email protected]
 
-
-
 normative:
 
 informative:
 
-
 --- abstract
 
 The increasing prevalence of cloud computing and micro service architectures has led to the rise of complex software functions being built and deployed as workloads, where a workload is defined as a running instance of software executing for a specific purpose.
@@ -92,7 +89,7 @@ How the workload obtains identity information and interacts with the agent is su
   | Host Operating System and Hardware                   |
   +------------------------------------------------------+
 ~~~~
-{: #arch-fig title="Host Software Layinger in a Workload Identity Architecture."}
+{: #arch-fig title="Host Software Layering in a Workload Identity Architecture."}
 
 Once the workload is started and has obtained unique identity information, it can offer its services. Once a service is invoked on a workload it may require interaction with other workloads. An example of such interaction is shown in {{?I-D.ietf-oauth-transaction-tokens}} where an externally-facing endpoint is invoked using conventional authorization mechanism, such as an OAuth 2.0 access token. The interaction with other workload may require the security context to be passed along the call chain.