Commit 215f18eb authored by Alison Wilbur's avatar Alison Wilbur Committed by Marc Gravell

Fix indentation on Basics.md (#835)

Fix indentation level on a nested list.
parent a1a834f6
...@@ -122,9 +122,9 @@ There are 3 primary usage mechanisms with StackExchange.Redis: ...@@ -122,9 +122,9 @@ There are 3 primary usage mechanisms with StackExchange.Redis:
- Synchronous - where the operation completes before the methods returns to the caller (note that while this may block the caller, it absolutely **does not** block other threads: the key idea in StackExchange.Redis is that it aggressively shares the connection between concurrent callers) - Synchronous - where the operation completes before the methods returns to the caller (note that while this may block the caller, it absolutely **does not** block other threads: the key idea in StackExchange.Redis is that it aggressively shares the connection between concurrent callers)
- Asynchronous - where the operation completes some time in the future, and a `Task` or `Task<T>` is returned immediately, which can later: - Asynchronous - where the operation completes some time in the future, and a `Task` or `Task<T>` is returned immediately, which can later:
- be `.Wait()`ed (blocking the current thread until the response is available) - be `.Wait()`ed (blocking the current thread until the response is available)
- have a continuation callback added ([`ContinueWith`](http://msdn.microsoft.com/en-us/library/system.threading.tasks.task.continuewith(v=vs.110).aspx) in the TPL) - have a continuation callback added ([`ContinueWith`](http://msdn.microsoft.com/en-us/library/system.threading.tasks.task.continuewith(v=vs.110).aspx) in the TPL)
- be *awaited* (which is a language-level feature that simplifies the latter, while also continuing immediately if the reply is already known) - be *awaited* (which is a language-level feature that simplifies the latter, while also continuing immediately if the reply is already known)
- Fire-and-Forget - where you really aren't interested in the reply, and are happy to continue irrespective of the response - Fire-and-Forget - where you really aren't interested in the reply, and are happy to continue irrespective of the response
The synchronous usage is already shown in the examples above. This is the simplest usage, and does not involve the [TPL][1]. The synchronous usage is already shown in the examples above. This is the simplest usage, and does not involve the [TPL][1].
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment