Refactor context API documentation for clarity and consistency

Author: Luuk Peters

16/umbraco-cms/customizing/foundation/context-api/consume-a-context.md

@@ -215,10 +215,10 @@ This example creates an example service that can show a notification in the back
 import { UmbControllerBase } from '@umbraco-cms/backoffice/class-api';
 import { UMB_NOTIFICATION_CONTEXT } from '@umbraco-cms/backoffice/notification';
 
-//The example element extends the UmbLitElement (which is the same as UmbElementMixin(LitElement))
-//This gives us all the helpers we need to get or consume contexts
+// This service class extends UmbControllerBase
+// This gives us access to getContext() and consumeContext()
 export default class ExampleService extends UmbControllerBase {
-    async ShowNotification(notificationText) {
+    async showNotification(notificationText) {
 
         //We try to get an instance of the context
         const notificationContext = await this.getContext(UMB_NOTIFICATION_CONTEXT);
@@ -253,7 +253,7 @@ export class ExampleService extends UmbControllerBase {
     constructor(host) {
         super(host);
 
-        // Subscribe to the notification context
+        // Subscribe to the document workspace context
         this.consumeContext(UMB_DOCUMENT_WORKSPACE_CONTEXT, (context) => {
             if (context) {
                 console.log("I've got the document workspace context: ", context);

16/umbraco-cms/customizing/foundation/context-api/context-api-fundamentals.md

@@ -28,7 +28,7 @@ The Context API exists to solve common problems in complex user interfaces:
 To understand the Context API, it's important to understand the terminology that is used in the rest of the documentation.
 
 ### Context
-An object that encapsulates both data and methods to interact with that data. This object can be provided to descending DOM elements. A context represents a specific capability or state that multiple elements might need to access. Examples include workspace context, content data, user permissions, or specialized services. Contexts encapsulate both data and methods, making them more than simple data containers. Unlike repositories, a context is always only available within the scope of a certain element and it's descendants.
+An object that encapsulates both data and methods to interact with that data. This object can be provided to descending DOM elements. A context represents a specific capability or state that multiple elements might need to access. Examples include workspace context, content data, user permissions, or specialized services. Contexts encapsulate both data and methods, making them more than simple data containers. Unlike repositories, a context is always only available within the scope of a certain element and its descendants.
 
 ### Context provider
 An element that creates and makes a context available to its descending elements. The provider is responsible for the context's lifecycle. One element can provide multiple different contexts if needed.