Skip to content

Commit

Permalink
docs(101): rewording, formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
alexcg1 committed Jun 17, 2020
1 parent 9ce4443 commit 4d9103c
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/chapters/101/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,17 +46,17 @@ Let's say you're building a recipe search engine. For each recipe, the search en

* Ingredients
* Rating
* Type of cuisine - Chinese, American
* Type of cuisine - Chinese, American, French, and so on
* Type of dish - starter, main, dessert, snack
* Method to make the food

When a human sees a recipe, we can tell which part is the ingredients and which is the method. If we see the title "Lamb chops with mashed potato", we know it's likely a main and certainly not vegetarian. Most computers aren't that smart.
When a human sees a recipe, we can tell which part is the ingredients and which is the method. If we see the title *Lamb chops with mashed potato*, we know it's likely a main and certainly not vegetarian. Most computers aren't that smart.

For a **traditional search engine**, we'd have to write rules so the search engine could decipher each recipe into something structured that it can understand. And if we input a recipe in a slightly different format, it may not understand at all. And if you want to search something different next time? Back to the drawing board!
For a **traditional search engine**, we'd have to write rules so the search engine could decipher each recipe into something structured that it can understand. And if we input a recipe in a slightly different format, it may not understand at all. How about if you want to search something different next time? Back to the drawing board!

In a **neural search engine**, we start by feeding it a small list of recipes, labelling the author, ingredients, cuisine type, and so on. Instead of telling our neural network the rules, we just tell it the labels for this small set of data, like you'd teach a toddler animals by showing them pictures of cats and dogs and saying "cat" or "dog". After a while, they'd be able to see a new picture of a cat or dog and say what it is themselves. Our neural net is the same - show it a few labelled recipes, and it can identify recipes it's never seen before, without having to learn any rules.
In a **neural search engine**, we start by feeding it a small list of recipes, labelling the author, ingredients, cuisine type, and so on. Instead of telling our neural network the rules, we just tell it the labels for this small set of data, like you'd teach a toddler animals by showing them pictures of cats and dogs and saying "cat" or "dog". After a while, they'd be able to see a new picture and say what it is themselves. Our neural net is the same - show it a few labelled recipes, and it can understand recipes it's never seen before, without having to learn any rules.

Of course, it's not just recipes. Jina can handle all kinds of data, like numbers, text, code, coordinates, voice, music, images, videos, genetic samples, and much, much more.
Of course, it's not just recipes. Jina can handle all kinds of data, like numbers, text, code, coordinates, voice, music, images, videos, genetic sequences, and much, much more.

<h2 align="center">How Does Jina Work?</h2>

Expand Down

0 comments on commit 4d9103c

Please sign in to comment.