Fixing up the readme again

Author: gja

Readme.md

@@ -43,20 +43,22 @@ type User {
    id: ID!
    firstName: String!
    lastName: String!
-#  fullName: String @lambda
+   fullName: String @lambda
 }
+
 type Todo {
    id: ID!
    title: String
 }
-#type Query {
-#  todoTitles: [String] @lambda
-#}
+
+type Query {
+  todoTitles: [String] @lambda
+}
 ```
 
 ```bash
 # host.docker.internal may not work on old versions of docker
-docker run -it --rm -p 8686:8686 -v /path/to/script.js:/app/script.js -e DGRAPH_URL=http://host.docker.internal:8080 tdinkar/omega
+docker run -it --rm -p 8686:8686 -v /path/to/script.js:/app/script.js -e DGRAPH_URL=http://host.docker.internal:8080 dgraph/dgraph-lambda
 ```
 
 Note for linux: host.docker.internal doesn't work on older versions of docker on linux. You can use `DGRAPH_URL=http://172.17.0.1:8080` instead
@@ -80,6 +82,10 @@ We are trying to make the environment match the environment you'd get from Servi
 
 If you would like to add libraries, then use webpack --target=webworker to compile your script. We'll fill out these instructions later.
 
+### Working with Typescript
+
+You can import @slash-graph/lambda-types to get types for `addGraphQLResolver` and `addGraphQLMultiParentResolver`.
+
 ## Security
 
 Currently, this uses node context to try and make sure that users aren't up to any fishy business. However, contexts aren't true security, and we should eventually switch to isolates. In the meanwhile, we will basically have kube kill this if it takes a lot of CPU for say 5 secs
@@ -88,4 +94,4 @@ Currently, this uses node context to try and make sure that users aren't up to a
 
 Currently, the publishing of this isn't automated. In order to publish:
 * Publish the types in slash-graphql-lambda-types if needed with (npm version minor; npm publish)
-* Publish the docker image with docker build . -t dgraph/dgraph-lambda; docker push dgraph/dgraph-lambda
+* The docker-image auto publishes, but pushing a tag will create a tagged version that is more stable