change in website dir to trigger preview generation

docs/api-bridging/spec.md

@@ -12,7 +12,7 @@ In any Desktop Agent bridging scenario, it is expected that each DA is being ope
 
 * Clarified that collated response messages should have their own `meta.responseGuid` generated by the DAB
   * Corrected some related issues in the message handling pseudocode
-* Add message exchange for getAppMetadata
+* Added message exchange for getAppMetadata
 * Added a `meta.errorDetails` array to response messages that are collated
 * Added a `BridgingError` enumeration to the error enumerations to provide messages for workflows broken by disconnect or where response from a particular DA times out.
 * Add notes on how to handle `raiseIntentForContext` via the `findIntentByContext` and `raiseIntent` flows.
@@ -22,7 +22,6 @@ In any Desktop Agent bridging scenario, it is expected that each DA is being ope
 ## TODO list
 
 * Complete message exchange documentation for PrivateChannels
-
 * Expand on how the DAB should create the JWT token (and its claims, which must change to avoid replay attacks) which it sends out in the `hello` message for DAs to validate.
 * To create final PR:
   * Add new terms and acronyms to FDC3 glossary and ensure they are defined in this spec's introduction

website/README.md

@@ -287,3 +287,4 @@ iOS doesn't currently (July 2019) support .webp image files - so use .png - and
 # Full Documentation
 
 Full documentation can be found on the [website](https://docusaurus.io/).
+