adding some comments

Author: Marie Hoeger

README.md

@@ -8,5 +8,7 @@ The next step is to inlude function.json generation scripts in this project as w
 - npm install
 - npm start
 
+Check out app.ts code
+
 ### Disclaimer
 I wanted to show that code in `common` and `functions` can be structured however you like. Worth thinking about what pattern we actually want to encourage, especially with how we want to do templates.

src/functions/goodbye.ts

@@ -2,6 +2,7 @@ import { AzureFunction, Context } from "@azure/functions"
 import { Function2, HttpTrigger, BlobInput } from "../../future_node_modules/functions/azure-functions"
 import { CookiedRequest } from "../common/interfaces"
 
+// More traditional look of an Azure Function + registering by creating a "Function2" object
 const farewell: AzureFunction = async function (context: Context): Promise<void> {    
     // Log info from request cookie
     const req = context.req as CookiedRequest;

src/functions/hello.ts

@@ -2,6 +2,7 @@ import { Function2, HttpTrigger, BlobInput } from "../../future_node_modules/fun
 import { NamedContext } from "../common/interfaces"
 import { createResponse } from "../common/talkToPerson"
 
+// Newer look of an Azure Function. Note that it may be dangerous to not call "context.done" or forget to declare async
 export const helloFunction = new Function2(new HttpTrigger("api/hi", ["GET"]))
     .bindInputs([
         new BlobInput("blobInput")