Skip to content

Commit 70f854b

Browse files
committed
Fixed spellings mistakes in README.md
1 parent 148f313 commit 70f854b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,28 +11,28 @@
1111
</p>
1212

1313
# Cleipnir.NET / Cleipnir Flows
14-
Cleipnir is a powerful **durable execution** .NET framework - ensuring your code will always execute to completetion **correctly**.
14+
Cleipnir is a powerful **durable execution** .NET framework - ensuring your code will always execute to completion **correctly**.
1515
* Makes C#-code behave correctly after a crash, restart or suspension
1616
* Wait for external events directly inside your code
1717
* Suspend code execution for minutes, hours, weeks or longer
1818
* Requires only a database
1919
* Great performance compared to external workflow orchestration
2020
* Use with ASP.NET / generic host service
2121
* Integrates easily with all message-brokers and service-buses
22-
* Removes need for **saga-pattern** and **outbox-pattern**
23-
* Powerful alterrnative to job-schedulers (HangFire, Quartz)
22+
* Removes the need for **saga-pattern** and **outbox-pattern**
23+
* Powerful alternative to job-schedulers (HangFire, Quartz)
2424

2525
## Abstractions
2626
Cleipnir.NET provides the following 3 abstractions:
2727
### Capture
28-
Remembers the result of arbitary code:
28+
Remembers the result of arbitrary code:
2929
```csharp
3030
var transactionId = await Capture("TransactionId", () => Guid.NewGuid());
3131
//or simply
3232
var transactionId = await Capture(Guid.NewGuid);
3333
```
3434
### Messages
35-
Wait for retrival of external message - without taking up resources:
35+
Wait for retrieval of external message - without taking up resources:
3636
```csharp
3737
var fundsReserved = await Messages<FundsReserved>(timesOutIn: TimeSpan.FromMinutes(5));
3838
```
@@ -97,7 +97,7 @@ public class OrderFlow(
9797
Durable execution is an emerging paradigm for simplifying the implementation of code which can safely resume execution after a process crash or restart (i.e. after a production deployment).
9898
It allows the developer to implement such code using ordinary C#-code with loops, conditionals and so on.
9999

100-
Furthermore, durable execution allows suspending code execution for an arbitraty amount of time - thereby saving process resources.
100+
Furthermore, durable execution allows suspending code execution for an arbitrary amount of time - thereby saving process resources.
101101

102102
Essentially, durable execution works by saving state at explicitly defined points during the invocation of code, thereby allowing the framework to skip over previously executed parts of the code when/if the code is re-executed. This occurs both after a crash and suspension.
103103

0 commit comments

Comments
 (0)