updated incorrect description of input object

[bhargavyagnik]

Old
// responses is an array of the following structure:
// {
// response: string;
// context?: string;
// }

The error obtained in running the code :
universal-sentence-encoder:17 Uncaught (in promise) TypeError: e.normalize is not a function
at universal-sentence-encoder:17
at c.encode (universal-sentence-encoder:17)
at universal-sentence-encoder:17
at Array.map ()
at j.tokenizeStrings (universal-sentence-encoder:17)
at universal-sentence-encoder:17
at tfjs:17
at e.t.scopedRun (tfjs:17)
at e.t.tidy (tfjs:17)
at Object.bx [as tidy] (tfjs:17)

This error is due to the incorrect object definition of "input"
On observation of the code of universal-sentence-encoder, we see that

embed(e) {
            const n = t.tidy(()=>{
                const t = this.tokenizeStrings(e.queries, f)
                  , n = this.tokenizeStrings(e.responses, f);
                if (null != e.contexts && e.contexts.length !== e.responses.length)
                    throw new Error("The length of response strings and context strings need to match.");
                const o = e.contexts || [];

---

So e.queries and e.contexts show that the input object should be

input =
{
    queries: string[],
    responses: string[],
    contexts:string[]
}

So that is what I propose to be updated in the readme

---

This change is 

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[bhargavyagnik]

@googlebot I signed it!

[jenperson]

Reviewed 1 of 1 files at r1.
Reviewable status: 0 of 1 approvals obtained (waiting on @bhargavyagnik)

---

universal-sentence-encoder/README.md line 102 at r1 (raw file):

  //    queries:string[];
  //    responses:string[];
  //    context:string[];   

This should be contexts

---

universal-sentence-encoder/README.md line 104 at r1 (raw file):

  //    context:string[];   
  // }
  // context is optional, it provides the context string of the answer.

contexts*