Update async/await guidelines based on feedback from paulloz

Author: carrollj

tutorials/scripting/c_sharp/c_sharp_basics.rst

@@ -394,7 +394,7 @@ Using ``async``/``await``
 
 You might face a scenario where you must ``await`` a method call.
 You will notice that when you use ``await``, you are required to mark the method you use it in as ``async``, 
-and change the return type to ``Task`` or ``Task<T>``. 
+and change the return type to an awaitable type, such as ``Task`` or ``Task<T>``. 
 Consequently, you must call your now ``async`` method using ``await``, 
 which propagates the problem all the way up the call chain.
 This is why many people compare ``async``/``await`` to a "zombie virus", 
@@ -416,8 +416,8 @@ To compare these options, we will work with the following script:
 
     public partial class AsyncTestNode : Node
     {
-        int _taskCount = 0;
-        DateTime start;
+        private int _taskCount = 0;
+        private DateTime start;
         public override void _Ready()
         {
             start = DateTime.Now;
@@ -524,8 +524,8 @@ Here is a pattern you can adopt to avoid race conditions:
         [Export] public int EntityID { get; set; } = 1;
     
         readonly SomeCustomRepository _db = new();
-        int _health;
-        bool _init;
+        private int _health;
+        private bool _init;
     
         // We will check IsInvalid after we await async methods
         // Otherwise we risk the continuation running in a disposed context