Skip to content

Commit d8bfdf8

Browse files
Update README.md
1 parent db06941 commit d8bfdf8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,11 @@ There is a 50 minute talk that covers this on [YouTube](https://www.youtube.com/
1717

1818
There is a rudimentary "retail bank accounts" example (as a Blazor front end) [here](https://retailbank.z6.web.core.windows.net/) ( [source repository on github](https://github.com/MerrionComputing/CloudBank) ) that demonstrates the different types of operation on an event stream and the source code for that is included in this repository. This is an entirely serverless system with no underlying database which does "scale to zero".
1919

20-
## End goal
20+
## How to use
2121

22-
The goal is to be able to interact with the event streams for entities without any extra plumbing in the azure function itself - with both access to event streams and to run projections being via bound variables that are instantiated when the azure function is executed.
22+
This library allows you to interact with the event streams for entities without any extra plumbing in the azure function itself - with both access to event streams and to run projections being via bound variables that are instantiated when the azure function is executed.
2323

24-
To add events to an event stream you would use an *Event stream* attribute and class thus:-
24+
To add events to an event stream you use an *Event stream* attribute and class thus:-
2525

2626
```csharp
2727
[FunctionName("OpenAccount")]
@@ -53,7 +53,7 @@ public static async Task<HttpResponseMessage> OpenAccountRun(
5353
}
5454
```
5555

56-
To get the values out of an event stream you would use a *Projection* attribute and class thus:-
56+
To get the values out of an event stream you use a *Projection* attribute and class thus:-
5757

5858
```csharp
5959
[FunctionName("GetBalance")]

0 commit comments

Comments
 (0)