From bed6fac538e91d306892456c113ac758aac29ea0 Mon Sep 17 00:00:00 2001
From: Jim Aho <jiim.aho@gmail.com>
Date: Wed, 7 Mar 2018 22:47:33 +0100
Subject: [PATCH] Swap params (#369)

Fixes expected vs actual arguments passed to `Assert.AreEqual`.
---
 docs/help/_posts/2010-02-03-return-for-any-args.markdown | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/help/_posts/2010-02-03-return-for-any-args.markdown b/docs/help/_posts/2010-02-03-return-for-any-args.markdown
index 168e68859..57bbe6d1e 100644
--- a/docs/help/_posts/2010-02-03-return-for-any-args.markdown
+++ b/docs/help/_posts/2010-02-03-return-for-any-args.markdown
@@ -16,8 +16,8 @@ A call can be configured to return a value regardless of the arguments passed us
 
 {% examplecode csharp %}
 calculator.Add(1, 2).ReturnsForAnyArgs(100); 
-Assert.AreEqual(calculator.Add(1, 2), 100);
-Assert.AreEqual(calculator.Add(-7, 15), 100);
+Assert.AreEqual(100, calculator.Add(1, 2));
+Assert.AreEqual(100, calculator.Add(-7, 15));
 {% endexamplecode %}
 
 The same behaviour can also be achieved using [argument matchers](/help/argument-matchers): it is simply a shortcut for replacing each argument with `Arg.Any<T>()`.