Remove product references; typos

Signed-off-by: Rachel Myers <rachelmyers@google.com>

spec.md

@@ -45,11 +45,11 @@ systems that allow cloud providers, third-party tools and services to provide:
 - Trigger configuration allows for actions to be invoked based on a condition
 (e.g. for a specific event type generated by a source, optionally filtered by
 specific attribute values, such as a Function which is invoked when an image is
-uploaded to specific S3 or Google Cloud Storage “bucket” path)
+uploaded to a specific bucket in an object store).
 - Events are uniquely identified to facilitate developer velocity and tooling:
-  - a unique idenfier allows for idempotency for reliable implementation
+  - a unique identifier allows for idempotency for reliable implementation
   - structured event definitions allow the consumer to rely on a specific format
-- Common metadata attributes allow for observability via tools whithout
+- Common metadata attributes allow for observability via tools without
 knowledge of the specific implementation of an event system and also can provide
 value without detailed handling of the specifics of the unique event data
 - CloudEvents may be transported from source to action with different protocols.
@@ -66,8 +66,8 @@ systems to easily react to changes in a source that they do not control. The
 *source* and action are often built by different developers.
 
 Examples:
-- the *source* is a managed service and the *action* is custom
-code in a serverless Function (such as AWS Lambda or Google Cloud Functions).
+- the *source* is a managed service and the *action* is custom code in a
+serverless Function.
 - the *source* is an IoT device and the *event* is transmitted through an API
 Gateway to the *action*, a service provided by a different developer.