Repository: alttester/AltTester-Unity-SDK (language: python)

Issue:
Adapt py test and example for GetStaticProperty to be aplicable for iOS too
The python test for the `GetStaticProperty` command cannot be used for iOS and needs to be adapted to work. It also needs to be updated in the documentation because the example contains the same test.
  
  ![image](https://gitlab.com/altom/altunity/altunitytester/uploads/8c5a57a4d5d36976221388991194b298/image.png)

---
<sub>You can find the original issue from GitLab [here](https://gitlab.com/altom/altunity/altunitytester/-/issues/746).</sub>



Discussion / hints:
Triaged Week no. 40, 2023. 
@iulianatodoran if the test is updated, it only needs to be updated in the documentation. 

Fix patch:
diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md
index a8fcdb9f5..bc80d04d6 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.md
+++ b/.github/ISSUE_TEMPLATE/bug-report.md
@@ -13,7 +13,7 @@ assignees: ''
 **What version of Unity are you using?**
 (2019.4.40f1, 2020.3.31f1, 2020.3.40f1, 2021.3.2f1, 2021.3.11f1, etc)
 
-**What version of AltTester Unity SDK are you using?**
+**What version of AltTester® Unity SDK are you using?**
 (1.6.6, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.8.1, 1.8.2, 2.0.0, 2.0.1, 2.0.2)
 
 **On what device are you trying to run the test?**
diff --git a/Assets/AltTester/README.md b/Assets/AltTester/README.md
index 2aa9a6613..41dbeb255 100644
--- a/Assets/AltTester/README.md
+++ b/Assets/AltTester/README.md
@@ -1,6 +1,6 @@
-# AltTester Unity SDK
+# AltTester® Unity SDK
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
 
 ## Documentation
 
diff --git a/Assets/AltTester/Runtime/Prefab/AltTesterPrefab.prefab b/Assets/AltTester/Runtime/Prefab/AltTesterPrefab.prefab
index 13d93725c..8ed9de5e3 100644
--- a/Assets/AltTester/Runtime/Prefab/AltTesterPrefab.prefab
+++ b/Assets/AltTester/Runtime/Prefab/AltTesterPrefab.prefab
@@ -159,7 +159,7 @@ MonoBehaviour:
     m_HorizontalOverflow: 0
     m_VerticalOverflow: 0
     m_LineSpacing: 1
-  m_Text: AltTester v.2.0.2
+  m_Text: "AltTester\xAE v.2.0.2"
 --- !u!1 &1307030318267323383
 GameObject:
   m_ObjectHideFlags: 0
diff --git a/Assets/AltTester/Runtime/UI/AltDialog.cs b/Assets/AltTester/Runtime/UI/AltDialog.cs
index c193d3065..595c4af16 100644
--- a/Assets/AltTester/Runtime/UI/AltDialog.cs
+++ b/Assets/AltTester/Runtime/UI/AltDialog.cs
@@ -88,7 +88,7 @@ protected void Start()
         {
             Dialog.SetActive(InstrumentationSettings.ShowPopUp);
 
-            SetTitle("AltTester v." + AltRunner.VERSION);
+            SetTitle("AltTester® v." + AltRunner.VERSION);
             SetUpCloseButton();
             SetUpIcon();
             SetUpHostInputField();
diff --git a/Assets/Editor/CreateAltPrefab.cs b/Assets/Editor/CreateAltPrefab.cs
index f4b7e61a2..5e1ac34cb 100644
--- a/Assets/Editor/CreateAltPrefab.cs
+++ b/Assets/Editor/CreateAltPrefab.cs
@@ -305,7 +305,7 @@ public static Text CreateTitle(RectTransform parent, string version = "2.0.x")
             TitleRectTransform.pivot = new Vector2(0.5f, 1f);
 
             var TitleText = TitleGameObject.GetComponent<Text>();
-            TitleText.text = "AltTester v." + version;
+            TitleText.text = "AltTester® v." + version;
             TitleText.fontSize = 30;
             TitleText.color = Color.white;
             TitleText.alignment = TextAnchor.MiddleCenter;
diff --git a/Assets/README.md b/Assets/README.md
index 2aa9a6613..41dbeb255 100644
--- a/Assets/README.md
+++ b/Assets/README.md
@@ -1,6 +1,6 @@
-# AltTester Unity SDK
+# AltTester® Unity SDK
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
 
 ## Documentation
 
diff --git a/Bindings~/dotnet/AltDriver/AltDriver.csproj b/Bindings~/dotnet/AltDriver/AltDriver.csproj
index 0d9f44727..d84b900b0 100644
--- a/Bindings~/dotnet/AltDriver/AltDriver.csproj
+++ b/Bindings~/dotnet/AltDriver/AltDriver.csproj
@@ -8,10 +8,10 @@
         <PackageVersion Condition="'$(PACKAGE_VERSION)' != ''">$(PACKAGE_VERSION)</PackageVersion>
         <Title>AltTester-Driver</Title>
         <Description>
-            AltTester-Driver package includes the C# bindings needed to run tests against Unity apps using AltTester Unity SDK.
+            AltTester-Driver package includes the C# bindings needed to run tests against Unity apps using AltTester® Unity SDK.
         </Description>
         <Summary>
-            C# Bindings to allow tests to be run against Unity games and apps using AltTester Unity SDK
+            C# Bindings to allow tests to be run against Unity games and apps using AltTester® Unity SDK
         </Summary>
         <Authors> Altom </Authors>
 
diff --git a/Bindings~/dotnet/README.md b/Bindings~/dotnet/README.md
index 33edaf2f4..ae9b2f3d0 100644
--- a/Bindings~/dotnet/README.md
+++ b/Bindings~/dotnet/README.md
@@ -1,6 +1,6 @@
-# AltTester Unity SDK - .NET Bindings
+# AltTester® Unity SDK - .NET Bindings
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
 
 Read the documentation on https://altom.com/alttester/docs/pro/sdk/
 
diff --git a/Bindings~/java/README.md b/Bindings~/java/README.md
index 51d1229ab..b4503c56a 100644
--- a/Bindings~/java/README.md
+++ b/Bindings~/java/README.md
@@ -1,6 +1,6 @@
-# AltTester Unity SDK - Java Bindings
+# AltTester® Unity SDK - Java Bindings
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
 
 Read the documentation on https://alttester.com/docs/sdk/latest/
 
diff --git a/Bindings~/python/README.md b/Bindings~/python/README.md
index c9ae4ac34..da83d7b59 100644
--- a/Bindings~/python/README.md
+++ b/Bindings~/python/README.md
@@ -1,8 +1,8 @@
-# AltTester Python Bindings
+# AltTester® Python Bindings
 
-This package contains an library for adding Python language binding to the AltTester framework.
+This package contains an library for adding Python language binding to the AltTester® framework.
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
 
 You can run your tests on real devices (mobile, PCs, etc.) or inside the Unity Editor.
 
diff --git a/Bindings~/python/setup.py b/Bindings~/python/setup.py
index d167e6930..44afd56c6 100644
--- a/Bindings~/python/setup.py
+++ b/Bindings~/python/setup.py
@@ -19,7 +19,7 @@
 
 
 NAME = 'AltTester-Driver'
-DESCRIPTION = "Python bindings for the AltTester framework. AltTester is an open-source UI driven test " \
+DESCRIPTION = "Python bindings for the AltTester® framework. AltTester® is an open-source UI driven test " \
     "automation tool that helps you find objects in your game and interacts with them."
 URL = 'https://alttester.com/docs/sdk/latest/'
 EMAIL = 'contact@alttester.com'
diff --git a/Docs/README.md b/Docs/README.md
index 3953d902e..566e31742 100644
--- a/Docs/README.md
+++ b/Docs/README.md
@@ -1,4 +1,4 @@
-# AltTester Unity SDK Docs
+# AltTester® Unity SDK Docs
 
 ## Install
 
diff --git a/Docs/source/_static/img/advanced-usage/case1.png b/Docs/source/_static/img/advanced-usage/case1.png
index 36dbe436e..bccced783 100644
Binary files a/Docs/source/_static/img/advanced-usage/case1.png and b/Docs/source/_static/img/advanced-usage/case1.png differ
diff --git a/Docs/source/_static/img/advanced-usage/case2.png b/Docs/source/_static/img/advanced-usage/case2.png
index 29f935657..429c1d516 100644
Binary files a/Docs/source/_static/img/advanced-usage/case2.png and b/Docs/source/_static/img/advanced-usage/case2.png differ
diff --git a/Docs/source/_static/img/advanced-usage/case3.png b/Docs/source/_static/img/advanced-usage/case3.png
index ae3ad5a0a..aefe842d6 100644
Binary files a/Docs/source/_static/img/advanced-usage/case3.png and b/Docs/source/_static/img/advanced-usage/case3.png differ
diff --git a/Docs/source/_static/img/advanced-usage/case4.png b/Docs/source/_static/img/advanced-usage/case4.png
index 8781f18c1..7dbec8295 100644
Binary files a/Docs/source/_static/img/advanced-usage/case4.png and b/Docs/source/_static/img/advanced-usage/case4.png differ
diff --git a/Docs/source/_static/img/advanced-usage/case5.png b/Docs/source/_static/img/advanced-usage/case5.png
index 57d9b547f..3a5ecd953 100644
Binary files a/Docs/source/_static/img/advanced-usage/case5.png and b/Docs/source/_static/img/advanced-usage/case5.png differ
diff --git a/Docs/source/_static/img/overview/architecture1.png b/Docs/source/_static/img/overview/architecture1.png
index 1278a3ebc..49838d3ba 100644
Binary files a/Docs/source/_static/img/overview/architecture1.png and b/Docs/source/_static/img/overview/architecture1.png differ
diff --git a/Docs/source/_static/img/overview/architecture2.png b/Docs/source/_static/img/overview/architecture2.png
index 2b29bd984..4d0c4a254 100644
Binary files a/Docs/source/_static/img/overview/architecture2.png and b/Docs/source/_static/img/overview/architecture2.png differ
diff --git a/Docs/source/conf.py b/Docs/source/conf.py
index c68bc818f..945ddc7d1 100644
--- a/Docs/source/conf.py
+++ b/Docs/source/conf.py
@@ -21,7 +21,7 @@
 
 copyright = '2023, Altom Consulting'
 author = 'Altom'
-project = 'AltTester Unity SDK'
+project = 'AltTester® Unity SDK'
 
 # Before creating a new tag, add the new one here and update 'latest' with the new SDK tag in index.rst line 44
 # Currently there is no way to add in toctree a dynamic link based on the version.
diff --git a/Docs/source/home.rst b/Docs/source/home.rst
index 08450902f..478bbf1eb 100644
--- a/Docs/source/home.rst
+++ b/Docs/source/home.rst
@@ -1,7 +1,7 @@
-AltTester Unity SDK
+AltTester® Unity SDK
 ===================
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you
 find objects in your application and interacts with them using tests written in C#,
 Python or Java. You can run your tests on real devices (mobile, PCs, etc.) or
 inside the Unity Editor.
diff --git a/Docs/source/index.rst b/Docs/source/index.rst
index 8c0309026..ae593af77 100644
--- a/Docs/source/index.rst
+++ b/Docs/source/index.rst
@@ -1,22 +1,22 @@
-.. AltTester Unity SDK documentation master file, created by
+.. AltTester® Unity SDK documentation master file, created by
    sphinx-quickstart on Thu Oct 17 09:19:29 2019.
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
-AltTester
+AltTester®
 =========
 
-Through AltTester, we provide a UI Test Automation solution for Unity
+Through AltTester®, we provide a UI Test Automation solution for Unity
 applications.
 
-- AltTester Unity SDK is a free, open source asset. Its main goal is to enable UI
+- AltTester® Unity SDK is a free, open source asset. Its main goal is to enable UI
   test automation, by instrumenting applications to get access and programmatically
-  control the Unity objects. Get AltTester Unity SDK from
+  control the Unity objects. Get AltTester® Unity SDK from
   :alttestersdkdownload:`our website <>`.
 
-- AltTester Desktop is an application allowing users to inspect the
+- AltTester® Desktop is an application allowing users to inspect the
   object hierarchy and interact with their app outside the Unity Editor. Get
-  AltTester Desktop from :alttesterpage:`our website <>`.
+  AltTester® Desktop from :alttesterpage:`our website <>`.
 
 
 Documentation
@@ -30,7 +30,7 @@ Documentation
    *  :doc:`/pages/overview`
    *  :doc:`/pages/get-started`
 
-*  :altTesterdesktopdocumentation:`AltTester Desktop <home.html>`
+*  :altTesterdesktopdocumentation:`AltTester® Desktop <home.html>`
 
    *  :altTesterdesktopdocumentation:`Overview <pages/overview.html>`
    *  :altTesterdesktopdocumentation:`Get Started <pages/get-started.html>`
@@ -41,7 +41,7 @@ Documentation
    :hidden:
 
    home
-   AltTester Desktop <https://alttester.com/docs/desktop/v.2.0.2/home.html>
+   AltTester® Desktop <https://alttester.com/docs/desktop/v.2.0.2/home.html>
 
 
 .. toctree::
diff --git a/Docs/source/pages/advanced-usage.md b/Docs/source/pages/advanced-usage.md
index 013ffead2..b6c0e1f94 100644
--- a/Docs/source/pages/advanced-usage.md
+++ b/Docs/source/pages/advanced-usage.md
@@ -1,22 +1,22 @@
 # Advanced Usage
 
 This guide covers some of the more advanced features, patterns and
-configuration options of AltTester Unity SDK.
+configuration options of AltTester® Unity SDK.
 
 ## AltTester input
 
-AtTester Unity SDK has an `Input` class which overrides the Input class implemented by Unity. This way AltTester intercepts the input actions to be performed in the instrumented app and simulates them through this class.
+AtTester Unity SDK has an `Input` class which overrides the Input class implemented by Unity. This way AltTester® intercepts the input actions to be performed in the instrumented app and simulates them through this class.
 In case you are using assembly definitions inside your project, you will have to reference the `AltTesterUnitySDK.asmdef` in all your .asmdef files which use input actions.
 
 ## AltTester input vs. regular input
 
-AltTester's custom input is active, by default, in any instrumented build. This means that certain input related actions (the ones that are part of Unity's `Input` class) will be inactive for regular input (the device's input). Because of this, pressing a key from the keyboard for example will not have any effect on the app. However, the simulated input from the tests, like the `PressKey` command, will be able to manipulate the object within the scene. While the AltTester input is active, the icon from the right bottom corner is green. You can change this behaviour by clicking on the AltTester's icon and unchecking the box with the `AltTester Input` message. Now the icon will turn darker, signaling that the regular input is active. In this state, you can interfere with the object from the app using the keyboard or other input. Keep in mind that, input actions from the AltTester Desktop won't have any effect while regular input is active. At the same time, if you want to run some automated tests, the AltTester input will be activated automatically for you.
+AltTester®'s custom input is active, by default, in any instrumented build. This means that certain input related actions (the ones that are part of Unity's `Input` class) will be inactive for regular input (the device's input). Because of this, pressing a key from the keyboard for example will not have any effect on the app. However, the simulated input from the tests, like the `PressKey` command, will be able to manipulate the object within the scene. While the AltTester input is active, the icon from the right bottom corner is green. You can change this behaviour by clicking on the AltTester®'s icon and unchecking the box with the `AltTester Input` message. Now the icon will turn darker, signaling that the regular input is active. In this state, you can interfere with the object from the app using the keyboard or other input. Keep in mind that, input actions from the AltTester® Desktop won't have any effect while regular input is active. At the same time, if you want to run some automated tests, the AltTester input will be activated automatically for you.
 
 ## Build apps from the command line
 
 To build your Unity application from command line you need a static method in
 your project that handles the build logic. To instrument your Unity application
-with AltTester Unity SDK, your build method must define `ALTTESTER` scripting
+with AltTester® Unity SDK, your build method must define `ALTTESTER` scripting
 symbol and must insert AltTester Prefab in the first scene of the app.
 
 Depending on your project's setup, there are two ways in which apps can be
@@ -26,13 +26,13 @@ built from the command line:
 ```eval_rst
 .. note::
 
-    AltTester Unity SDK does not work by default in release mode. If you instrument
+    AltTester® Unity SDK does not work by default in release mode. If you instrument
     your app in release mode, AltTester Prefab self removes from the scenes and
     the socket server does not start. Best case practice is to customize your
     build script to insert AltTester Prefab only in Debug mode.
 
-    If you do want to use AltTester Unity SDK in release mode see
-    `Using AltTester Unity SDK in Release mode section <#using-alttester-unity-sdk-in-release-mode>`_.
+    If you do want to use AltTester® Unity SDK in release mode see
+    `Using AltTester® Unity SDK in Release mode section <#using-alttester-unity-sdk-in-release-mode>`_.
 
 ```
 
@@ -109,7 +109,7 @@ commands:
 
     .. tab:: C#
 
-        Available AltTester SDK command line arguments:
+        Available AltTester® SDK command line arguments:
 
         ``-testsClass`` - runs tests from given class/classes
 
@@ -183,7 +183,7 @@ commands:
 
 ## Run tests on a Continuous Integration Server
 
-1. Instrument your app build with AltTester Unity SDK from Unity or by [building from the command line](#build-apps-from-the-command-line).
+1. Instrument your app build with AltTester® Unity SDK from Unity or by [building from the command line](#build-apps-from-the-command-line).
 2. Start the app build on a device.
 3. Run your tests - see commands in the ["Run tests from the command line" section](#run-tests-from-the-command-line).
 
@@ -195,11 +195,11 @@ An example CI configuration file can be viewed in the [GitLab repository](https:
 Reverse port forwarding, is the behind-the-scenes process of intercepting
 data traffic and redirecting it from a device's IP and/or port to the computer's IP and/or port.
 
-When you run your app instrumented with AltTester Unity SDK on a device, you need
+When you run your app instrumented with AltTester® Unity SDK on a device, you need
 to tell your build how to connect to the AltServer.
 
 Reverse port forwarding can be set up either through the command line or in the
-test code by using the methods available in the AltTester SDK classes.
+test code by using the methods available in the AltTester® SDK classes.
 
 The following are some cases when reverse port forwarded is needed:
 
@@ -213,7 +213,7 @@ The following are some cases when reverse port forwarded is needed:
 Reverse port forwarding can be set up in two ways:
 
 - through the command line using ADB
-- in the test code by using the methods available in the AltTester SDK classes
+- in the test code by using the methods available in the AltTester® SDK classes
 
 All methods listed above require that you have ADB installed.
 
@@ -318,11 +318,11 @@ In the routing table, the personal hotspot network would be secondary, therefore
 
 ```eval_rst
 .. note::
-    The default port on which the AltTester Unity SDK is running is 13000.
+    The default port on which the AltTester® Unity SDK is running is 13000.
     The port can be changed from the green popup. Make sure to press `Restart` after modifying its value.
 ```
 
-## Connect AltTester Unity SDK running inside the app to AltServer
+## Connect AltTester® Unity SDK running inside the app to AltServer
 
 There are multiple scenarios:
 
@@ -336,7 +336,7 @@ There are multiple scenarios:
 
 ![reverse port forwarding case 1](../_static/img/advanced-usage/case1.png)
 
-1. Start AltServer on your machine by opening AltTester Desktop. The server will be listening on port 13000 by default.
+1. Start AltServer on your machine by opening AltTester® Desktop. The server will be listening on port 13000 by default.
 2. Open your instrumented app on the same machine. It will automatically connect to AltServer. The server identifies the app using the **appName**.
 3. Connect your tests to the server using the line below in your **OneTimeSetup()**. Start your tests on the machine used before. Make sure that AltServer, the instrumented app and your tests are using **the same port**. Data transmission happens on localhost.
 
@@ -361,7 +361,7 @@ In this case **reverse port forwarding** is not needed as both the app and tests
 
 ![reverse port forwarding case 2](../_static/img/advanced-usage/case2.png)
 
-1. Start AltServer on your machine by opening AltTester Desktop. The server will be listening on port 13000 by default.
+1. Start AltServer on your machine by opening AltTester® Desktop. The server will be listening on port 13000 by default.
 2. Open your instrumented app on your device.
 3. Use [Reverse Port Forwarding](#what-is-reverse-port-forwarding-and-when-to-use-it) to direct the data traffic from the device's port to the computer's port. After this, your app will be connected to AltServer. The server identifies the app using the **appName**.
 4. Connect your tests to AltServer using the line below in your **OneTimeSetup()**. Start your tests on the machine used before. Make sure that AltServer, the instrumented app and your tests are using **the same port**. Data transmission happens on localhost.
@@ -385,7 +385,7 @@ In this case **reverse port forwarding** is not needed as both the app and tests
 
 ![reverse port forwarding case 3](../_static/img/advanced-usage/case3.png)
 
-1. Start AltServer on your machine by opening AltTester Desktop. The server will be listening on port 13000 by default.
+1. Start AltServer on your machine by opening AltTester® Desktop. The server will be listening on port 13000 by default.
 2. Open your instrumented app on your device. 
 3. Change the host from the green popup in your instrumented build to the machine's IP AltServer is running on. The server identifies the app using the **appName**.
 4. Connect your tests to AltServer using the line below in your **OneTimeSetup()**. Start your tests on the machine used before. Make sure that AltServer, the instrumented app and your tests are using **the same port**. Data transmission between tests and server happens on localhost; transmission between device and server happens on the host's IP.
@@ -412,7 +412,7 @@ In this case [Reverse Port Forwarding](#what-is-reverse-port-forwarding-and-when
 #### Connection through IP
 ![reverse port forwarding case 4](../_static/img/advanced-usage/case4.png)
 
-1. Start AltServer on your machine by opening AltTester Desktop. The server will be listening on port 13000 by default.
+1. Start AltServer on your machine by opening AltTester® Desktop. The server will be listening on port 13000 by default.
 2. Open your instrumented app on your devices. Make sure they have different names. In case you want to change the name, you can do that in the green popup. There is no need to make another instrumented build.
 3. Change the hosts from the green popups in your instrumented builds to the machine's IP AltServer is running on. The server identifies the apps using the **appName**.
 4. Connect your tests to AltServer using the line below in your **OneTimeSetup()**. You will need to create **2 AltDrivers** as you have 2 devices. AltDriver1 will communicate with device1 and AltDriver2 with device2. Start your tests on the machine used before. Make sure that AltServer, the instrumented app and your tests are using **the same port**. Data transmission between tests and server happens on localhost; transmission between devices and server happens on the host's IP.
@@ -451,7 +451,7 @@ Ex. with 2 Android devices:
 #### Connection through IP
 ![reverse port forwarding case 5](../_static/img/advanced-usage/case5.png)
 
-1. Start AltServer on your machine by opening AltTester Desktop. The server will be listening on port 13000 by default.
+1. Start AltServer on your machine by opening AltTester® Desktop. The server will be listening on port 13000 by default.
 2. Open your instrumented apps on your device. Make sure they have different names. In case you want to change the name, you can do that in the green popup. There is no need to make another instrumented build.
 3. Change the hosts from the green popups in your instrumented builds to the machine's IP AltServer is running on. The server identifies the apps using the **appName**.
 4. Connect your tests to AltServer using the line below in your **OneTimeSetup()**. You will need to create **2 AltDrivers** as you have 2 apps. AltDriver1 will communicate with app1 and AltDriver2 with app2. Start your tests on the machine used before. Make sure that AltServer, the instrumented app and your tests are using **the same port**. Data transmission between tests and server happens on localhost; transmission between device and server happens on the host's IP.
@@ -484,13 +484,13 @@ Use [Reverse Port Forwarding](#what-is-reverse-port-forwarding-and-when-to-use-i
     On mobile devices, AltDriver can interact only with a single app at a time and the app needs to be in focus. In case of 2 drivers and 2 apps, you need to switch (in your test scripts) between the applications. This is due to the fact that on Android/iOS only one application is in focus at a time, even when using split screen mode.
 ```
 
-## Using AltTester Unity SDK in Release mode
+## Using AltTester® Unity SDK in Release mode
 
-By default AltTester Unity SDK does not run in release mode. We recommended that you do not instrument your Unity application in release mode with AltTester Unity SDK. That being said, if you do want to instrument your application in release mode, you need to uncheck `RunOnlyInDebugMode` flag on AltRunnerPrefab inside AltTester Unity SDK asset folder `AltTester/Prefab/AltRunnerPrefab.prefab`
+By default AltTester® Unity SDK does not run in release mode. We recommended that you do not instrument your Unity application in release mode with AltTester® Unity SDK. That being said, if you do want to instrument your application in release mode, you need to uncheck `RunOnlyInDebugMode` flag on AltRunnerPrefab inside AltTester® Unity SDK asset folder `AltTester/Prefab/AltRunnerPrefab.prefab`
 
 ## Logging
 
-There are two types of logging that can be configured in AltTester Unity SDK. The logs from AltDriver (from the tests) and the logs from the AltTester Unity SDK (from the instrumented Unity application)
+There are two types of logging that can be configured in AltTester® Unity SDK. The logs from AltDriver (from the tests) and the logs from the AltTester® Unity SDK (from the instrumented Unity application)
 
 ```eval_rst
 .. note::
@@ -499,7 +499,7 @@ There are two types of logging that can be configured in AltTester Unity SDK. Th
 
 ```
 
-### AltTester Unity SDK logging
+### AltTester® Unity SDK logging
 
 Logging inside the instrumented Unity application is handled using a custom NLog LogFactory. The Server LogFactory can be accessed here: `AltTester.AltTesterUnitySDK.Logging.ServerLogManager.Instance`
 
@@ -572,17 +572,17 @@ Logging on the driver is handled using `NLog` in C#, `loguru` in python and `log
 
         Logging is handled via log4j. You can use log4j configuration files to customize your logging.
 
-        Setting the `enableLogging` in `AltDriver` initializes logger named `ro.AltTester` configured with two appenders, a file appender `AltFileAppender` and a console appender `AltConsoleAppender`
+        Setting the `enableLogging` in `AltDriver` initializes logger named `com.AltTester` configured with two appenders, a file appender `AltFileAppender` and a console appender `AltConsoleAppender`
 
         .. code-block:: java
 
             /* start AltDriver with logging enabled */
             altDriver = new AltDriver("127.0.0.1", 13000, true);
 
-            /* disable logging for ro.AltTester logger */
+            /* disable logging for com.AltTester logger */
             final LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
             final Configuration config = ctx.getConfiguration();
-            config.getLoggerConfig("ro.AltTester").setLevel(Level.OFF);
+            config.getLoggerConfig("com.AltTester").setLevel(Level.OFF);
 
             ctx.updateLoggers();
 
@@ -611,7 +611,7 @@ The logs for a WebGL instrumented build are displaied in the browser's console.
 
 ## Code Stripping
 
-AltTester Unity SDK is using reflection in some of the commands to get information from the instrumented application. If you application is using IL2CPP scripting backend then it might strip code that you would use in your tests. If this is the case we recommend creating an `link.xml` file. More information on how to manage code stripping and create an `link.xml` file is found in [Unity documentation](https://docs.unity3d.com/Manual/ManagedCodeStripping.html)
+AltTester® Unity SDK is using reflection in some of the commands to get information from the instrumented application. If you application is using IL2CPP scripting backend then it might strip code that you would use in your tests. If this is the case we recommend creating an `link.xml` file. More information on how to manage code stripping and create an `link.xml` file is found in [Unity documentation](https://docs.unity3d.com/Manual/ManagedCodeStripping.html)
 
 ## Generate testing reports using Allure
 
diff --git a/Docs/source/pages/commands.md b/Docs/source/pages/commands.md
index e8795f499..959ff0278 100644
--- a/Docs/source/pages/commands.md
+++ b/Docs/source/pages/commands.md
@@ -12,7 +12,7 @@ An AltDriver instance will connect to the running instrumented Unity application
 
 | Name           | Type    | Required | Description                                                                           |
 | -------------- | ------- | -------- | ------------------------------------------------------------------------------------- |
-| host           | string  | No       | The IP or hostname AltTester Unity SDK is listening on. The default value is "127.0.0.1". |
+| host           | string  | No       | The IP or hostname AltTester® Unity SDK is listening on. The default value is "127.0.0.1". |
 | port           | int     | No       | The default value is 13000.                                                           |
 | enableLogging  | boolean | No       | The default value is false.                                                           |
 | connectTimeout | int     | No       | The connect timeout in seconds.The default value is 60.                                |
@@ -1821,7 +1821,7 @@ Simulates device rotation action in your app.
 
 #### ResetInput
 
-Clears all active input actions simulated by AltTester.
+Clears all active input actions simulated by AltTester®.
 
 **_Parameters_**
 
@@ -2840,11 +2840,19 @@ Gets the value of the static field or property.
     .. code-tab:: py
 
         def test_get_static_property(self):
-            self.altdriver.load_scene('Scene 1 AltDriverTestScene')
-            self.altdriver.call_static_method("UnityEngine.Screen", "SetResolution", "UnityEngine.CoreModule", ["1920", "1080", "True"], ["System.Int32", "System.Int32", "System.Boolean"])
+
+            self.altdriver.call_static_method(
+                "UnityEngine.Screen", "SetResolution", "UnityEngine.CoreModule",
+                parameters=["1920", "1080", "True"],
+                type_of_parameters=["System.Int32",
+                                    "System.Int32", "System.Boolean"]
+            )
             width = self.altdriver.get_static_property(
-                "UnityEngine.Screen", "currentResolution.width", "UnityEngine.CoreModule")
-            self.assertEqual(int(width), 1920)
+                "UnityEngine.Screen", "currentResolution.width",
+                "UnityEngine.CoreModule"
+            )
+
+            assert int(width) == 1920
 
 ```
 
@@ -2908,7 +2916,7 @@ Sets the value of the static field or property.
 
 #### SetServerLogging
 
-Sets the level of logging on AltTester Unity SDK.
+Sets the level of logging on AltTester® Unity SDK.
 
 **_Parameters_**
 
@@ -3943,7 +3951,7 @@ None
 ```
 ### GetScreenPosition
 
- Returns the screen position of the AltTester object.
+ Returns the screen position of the AltTester® object.
 
 **_Parameters_**
 
@@ -3998,7 +4006,7 @@ None
 ```
 ### GetWorldPosition
 
-Returns the world position of the AltTester object.
+Returns the world position of the AltTester® object.
 
 **_Parameters_**
 
@@ -4256,7 +4264,7 @@ There are several characters that you need to escape when you try to find an obj
 
 ### AltId
 
-Is a solution offered by AltTester Unity SDK in order to find object easier. This is an unique identifier stored in an component and added to every object.
+Is a solution offered by AltTester® Unity SDK in order to find object easier. This is an unique identifier stored in an component and added to every object.
 **A limitation of this is that only the object already in the scene before building the app will have an AltId. Object instantiated during run time will not have an AltId**
 
 To add AltId to every object simply just click _Add AltId to every object_ from AltTester menu.
diff --git a/Docs/source/pages/contributing.md b/Docs/source/pages/contributing.md
index ef0fa5aef..2b6c0d6c4 100644
--- a/Docs/source/pages/contributing.md
+++ b/Docs/source/pages/contributing.md
@@ -1,6 +1,6 @@
 # Contributing
 
-First off, thank you for considering contributing to AltTester Unity SDK.
+First off, thank you for considering contributing to AltTester® Unity SDK.
 
 ## Leave a review
 
@@ -21,7 +21,7 @@ Try to:
 
 ## How to suggest a feature or enhancement?
 
-If you find yourself wishing for a feature that doesn’t exist in AltTester Unity SDK:
+If you find yourself wishing for a feature that doesn’t exist in AltTester® Unity SDK:
 
 -   Ensure the enhancement was not already reported by searching all issues.
 -   Open a [new issue](https://github.com/alttester/AltTester-Unity-SDK/issues/new?assignees=&labels=&template=feature-request.md&title=). Be sure to include a clear description of the feature you would like to see, as much relevant information as possible:
diff --git a/Docs/source/pages/examples.md b/Docs/source/pages/examples.md
index 6f6fdbf5d..47f39215a 100644
--- a/Docs/source/pages/examples.md
+++ b/Docs/source/pages/examples.md
@@ -1,6 +1,6 @@
 # Examples
 
-We used AltTester Unity SDK to test some sample apps to help you understand better how to use it.
+We used AltTester® Unity SDK to test some sample apps to help you understand better how to use it.
 We plan to add more examples in the near future. 
 
 ```eval_rst
@@ -29,20 +29,20 @@ We plan to add more examples in the near future.
 
 * Python tests [Multiplayer iOS / Android](https://github.com/alttester-test-examples/Python-Android-iOS-Multiplayer--AltTanks) -->
 
-**2.** Example test project for AltTester Unity SDK:
+**2.** Example test project for AltTester® Unity SDK:
 
 * C# tests [SampleScenes](https://alttester.com/app/uploads/AltTester/sdks/SampleScenes.unitypackage)
 
     Import this package under your AltTester package in Unity, to have access to the SampleScenes and C# tests.
 
 
-**3.** Example test projects for AltTester Unity SDK v.2.0.1 and the New Input System:
+**3.** Example test projects for AltTester® Unity SDK v.2.0.1 and the New Input System:
 
 * C# tests [CoinCollector](https://github.com/alttester/EXAMPLES-NewInputSystem--CoinCollector-CSharp)
 * C# tests [LeanTouch](https://github.com/alttester/EXAMPLES-NewInputSystem--LeanTouch-CSharp)
 * C# tests [RollABall](https://github.com/alttester/EXAMPLES-NewInputSystem--RollABall-CSharp)  
 
-<!-- **4.** Example test project for AltTester Unity SDK and Unity Test Framework:
+<!-- **4.** Example test project for AltTester® Unity SDK and Unity Test Framework:
 
 * C# tests [Endless Runner](https://github.com/alttester-test-examples/Unity-Test-Runner-AltTester)
 
diff --git a/Docs/source/pages/faq-troubleshooting.md b/Docs/source/pages/faq-troubleshooting.md
index 155c4c21c..0b0aaa967 100644
--- a/Docs/source/pages/faq-troubleshooting.md
+++ b/Docs/source/pages/faq-troubleshooting.md
@@ -1,7 +1,7 @@
 # FAQ
 
 <details>
-<summary> On what platforms can I run tests with AltTester Unity SDK? </summary>
+<summary> On what platforms can I run tests with AltTester® Unity SDK? </summary>
 <br>
 PC, Mac, Android, iOS and Unity Editor; support for WebGL and Consoles is work in progress.
 </details>
@@ -15,21 +15,21 @@ PC, Mac, Android, iOS and Unity Editor; support for WebGL and Consoles is work i
 <br>
 
 <details>
-<summary> Can AltTester Unity SDK be integrated with Appium?</summary>
+<summary> Can AltTester® Unity SDK be integrated with Appium?</summary>
 <br>
-Yes, AltTester Unity SDK can be used alongside Appium. Appium allows you to access the native objects and AltTester Unity SDK can be used to access the Unity objects.  For more info regarding how to run tests together with appium check <em><a href="alttester-with-appium.html">Running tests together with Appium</a></em>.
+Yes, AltTester® Unity SDK can be used alongside Appium. Appium allows you to access the native objects and AltTester® Unity SDK can be used to access the Unity objects.  For more info regarding how to run tests together with appium check <em><a href="alttester-with-appium.html">Running tests together with Appium</a></em>.
 </details>
 <br>
 
 <details>
-<summary> What versions of Unity does AltTester Unity SDK work with? </summary>
+<summary> What versions of Unity does AltTester® Unity SDK work with? </summary>
 <br>
-AltTester Unity SDK works with Unity 2020.3.0 or higher. If you encounter any issues we'd like to hear about them. You can <a href="contributing.html#did-you-find-a-bug">raise an issue</a> or join our community on <a href="https://discord.gg/Ag9RSuS">Discord</a> or <a href="https://groups.google.com/a/altom.com/g/alttesterforum">Google Groups</a>.
+AltTester® Unity SDK works with Unity 2020.3.0 or higher. If you encounter any issues we'd like to hear about them. You can <a href="contributing.html#did-you-find-a-bug">raise an issue</a> or join our community on <a href="https://discord.gg/Ag9RSuS">Discord</a> or <a href="https://groups.google.com/a/altom.com/g/alttesterforum">Google Groups</a>.
 </details>
 <br>
 
 <details>
-<summary>Can I use AltTester Unity SDK to run tests using device cloud services? </summary>
+<summary>Can I use AltTester® Unity SDK to run tests using device cloud services? </summary>
 <br>
 It works with some of the cloud services. We tried it with Bitbar Cloud and AWS Device Farm.
 These give you access to a virtual machine or a Docker container that has a cloud device attached, where you upload your tests, configure your environment and run your tests. More info about this here:<em><a href=" alttester-with-cloud.html"> Running tests using device cloud services.</a></em>
@@ -39,7 +39,7 @@ These give you access to a virtual machine or a Docker container that has a clou
 <details>
 <summary> Do I need access to the source code of the Unity App to write tests?</summary>
 <br>
-In order to run tests using AltTester Unity SDK you require an <a href="get-started.html#instrument-your-app-with-alttester-unity-sdk">instrumented build</a> of the Unity App. To create an instrumented build of the Unity App you need to <a href="get-started.html#import-alttester-package-in-unity-editor">import</a> the AltTester package in Unity Editor.
+In order to run tests using AltTester® Unity SDK you require an <a href="get-started.html#instrument-your-app-with-alttester-unity-sdk">instrumented build</a> of the Unity App. To create an instrumented build of the Unity App you need to <a href="get-started.html#import-alttester-package-in-unity-editor">import</a> the AltTester package in Unity Editor.
 </details>
 <br>
 
@@ -47,7 +47,7 @@ In order to run tests using AltTester Unity SDK you require an <a href="get-star
 <summary> I don’t have access to source code, but I do have access to an instrumented build. How can I begin to write tests?</summary>
 <br>
 ```eval_rst
-We’ve published AltTester Desktop, which allows you to inspect the app objects outside the unity editor without access to the source code. More information about AltTester Desktop can be found in this :altTesterdesktopdocumentation:`documentation <>`.
+We’ve published AltTester® Desktop, which allows you to inspect the app objects outside the unity editor without access to the source code. More information about AltTester® Desktop can be found in this :altTesterdesktopdocumentation:`documentation <>`.
 ```
 </details>
 <br>
@@ -57,14 +57,14 @@ We’ve published AltTester Desktop, which allows you to inspect the app objects
 <details>
 <summary> I get <strong>`waiting for connection on port 13000`</strong> popup message when i start my Unity App </summary>
 <br>
-The popup message shows up when you start your instrumented Unity App. It tells you that the AltTester Unity SDK is ready and you can start running your tests.
+The popup message shows up when you start your instrumented Unity App. It tells you that the AltTester® Unity SDK is ready and you can start running your tests.
 </details>
 <br>
 
 <details>
 <summary>I get the error: <strong>Multiple precompiled assemblies with the same name Newtonsoft.Json.dll included or the current platform.</strong> </summary>
 <br>
-You get this error due to multiple imports of Newtonsoft.Json.dll library. You can remove the Newtonsoft.Json version from AltTester Unity SDK by deleting the <em>Newtonsonft</em> folder <em>Assets/AltTester/3rdParty/Newtonsonft</em>.
+You get this error due to multiple imports of Newtonsoft.Json.dll library. You can remove the Newtonsoft.Json version from AltTester® Unity SDK by deleting the <em>Newtonsonft</em> folder <em>Assets/AltTester/3rdParty/Newtonsonft</em>.
 </details>
 <br>
 
@@ -113,14 +113,14 @@ If you have Addressables package included in your project, set the Addressables
 <br>
 
 <details>
-<summary>How can I <strong>use the Input from AltTester Unity SDK</strong> if my project is using <strong>Assembly Definitions </strong>?</summary>
+<summary>How can I <strong>use the Input from AltTester® Unity SDK</strong> if my project is using <strong>Assembly Definitions </strong>?</summary>
 <br>
-To use the Input from AltTester Unity SDK you have to reference <strong>AltTesterUnitySDK.asmdef</strong> in your .asmdef. In case you are using multiple assembly definitions you will have to reference our .asmdef in all of your .asmdef files which contain a reference to any kind of input (Unity's input or your custom built input).
+To use the Input from AltTester® Unity SDK you have to reference <strong>AltTesterUnitySDK.asmdef</strong> in your .asmdef. In case you are using multiple assembly definitions you will have to reference our .asmdef in all of your .asmdef files which contain a reference to any kind of input (Unity's input or your custom built input).
 </details>
 <br>
 
 <details>
-<summary> I downloaded the AltTester package v1.7.2 from the documentation on MacOS. I got a warning pop-up about the input system where I chose 'Yes' because I am using the New Input System. After reopening Unity Editor, <strong>AltTester Unity SDK is missing.</strong></summary>
+<summary> I downloaded the AltTester package v1.7.2 from the documentation on MacOS. I got a warning pop-up about the input system where I chose 'Yes' because I am using the New Input System. After reopening Unity Editor, <strong>AltTester® Unity SDK is missing.</strong></summary>
 <br>
 
 After reopening Unity Editor, add again the AltTester package in your project.
diff --git a/Docs/source/pages/get-started.md b/Docs/source/pages/get-started.md
index 104585e88..deb7f4f12 100644
--- a/Docs/source/pages/get-started.md
+++ b/Docs/source/pages/get-started.md
@@ -18,15 +18,15 @@ To run the first test for your Unity app you need to:
 
 ## Import AltTester package in Unity Editor
 
-To instrument your Unity application with AltTester Unity SDK you first need to import the AltTester package into Unity. This can be done either by downloading from the AltTester website, or by following the steps from the OpenUPM website.
+To instrument your Unity application with AltTester® Unity SDK you first need to import the AltTester package into Unity. This can be done either by downloading from the AltTester® website, or by following the steps from the OpenUPM website.
 
 ```eval_rst
 
 .. tabs::
 
-    .. tab:: UnityPackage from AltTester website
+    .. tab:: UnityPackage from AltTester® website
 
-        1. Download from :alttestersdkdownload:`AltTester <>`.
+        1. Download from :alttestersdkdownload:`AltTester® <>`.
         2. Import it by drag and drop inside your Unity project.
 
     .. tab:: UnityPackage from OpenUPM website
@@ -40,7 +40,7 @@ To instrument your Unity application with AltTester Unity SDK you first need to
 
 -   Newtonsoft.Json
 
-In order for AltTester Unity SDK to work you need dependency for Newtonsoft.Json. Add `"com.unity.nuget.newtonsoft-json": "3.0.1"` to your project `manifest.json`, inside `dependencies`.
+In order for AltTester® Unity SDK to work you need dependency for Newtonsoft.Json. Add `"com.unity.nuget.newtonsoft-json": "3.0.1"` to your project `manifest.json`, inside `dependencies`.
 
 ```json
 {
@@ -52,7 +52,7 @@ In order for AltTester Unity SDK to work you need dependency for Newtonsoft.Json
 
 -   Input System
 
-AltTester Unity SDK has support for Input System starting with version 1.7.1. To enable Input System in AltTester Unity SDK you need to add `"com.unity.inputsystem"` to your `manifest.json`, inside `testables.`
+AltTester® Unity SDK has support for Input System starting with version 1.7.1. To enable Input System in AltTester® Unity SDK you need to add `"com.unity.inputsystem"` to your `manifest.json`, inside `testables.`
 
 ```json
 {
@@ -62,7 +62,7 @@ AltTester Unity SDK has support for Input System starting with version 1.7.1. To
 
 -   Editor Coroutines
 
-In order for AltTester Unity SDK to work with your project you need the dependency for Editor Coroutines. Add `"com.unity.editorcoroutines": "1.0.0` to your project `manifest.json`, inside `dependencies`.
+In order for AltTester® Unity SDK to work with your project you need the dependency for Editor Coroutines. Add `"com.unity.editorcoroutines": "1.0.0` to your project `manifest.json`, inside `dependencies`.
 
 ```json
 {
@@ -73,11 +73,11 @@ In order for AltTester Unity SDK to work with your project you need the dependen
 ```
 
 <!--
-To instrument your Unity application with AltTester Unity SDK you first need to import the AltTester package into Unity.
+To instrument your Unity application with AltTester® Unity SDK you first need to import the AltTester package into Unity.
 
 ```eval_rst
 
-    1. Download `AltTester Unity SDK <https://alttester.com/app/uploads/altUnityProAlpha/AltUnityTesterUnityPackage>`_.
+    1. Download `AltTester® Unity SDK <https://alttester.com/app/uploads/altUnityProAlpha/AltUnityTesterUnityPackage>`_.
 
     2. Import it by drag and drop inside your Unity project.
 
@@ -92,9 +92,9 @@ To instrument your Unity application with AltTester Unity SDK you first need to
 
 ```
 
-![Window menu with AltTester Unity SDK Options](../_static/img/get-started/downloading-importing-alttester-editor.png)
+![Window menu with AltTester® Unity SDK Options](../_static/img/get-started/downloading-importing-alttester-editor.png)
 
-## Instrument your app with AltTester Unity SDK
+## Instrument your app with AltTester® Unity SDK
 
 Steps:
 
@@ -110,7 +110,7 @@ Steps:
 
 .. important::
 
-    AltTester Unity SDK is intended to be used only in debug builds, and it will not work in release mode out of the box. You need to make sure you don't release a production build instrumented with AltTester Unity SDK.
+    AltTester® Unity SDK is intended to be used only in debug builds, and it will not work in release mode out of the box. You need to make sure you don't release a production build instrumented with AltTester® Unity SDK.
 
 .. note::
 
@@ -148,7 +148,7 @@ Steps:
 
 ## Start the AltServer Module
 
-The AltServer Module is incorporated in AltTester Desktop. In order to start it, all you have to do is to open AltTester Desktop.
+The AltServer Module is incorporated in AltTester® Desktop. In order to start it, all you have to do is to open AltTester® Desktop.
 
 ## Run your app in Unity or on desired platform
 
@@ -208,7 +208,7 @@ Before running your tests you need to start the instrumented Unity application.
 
 .. note::
 
-    You can switch between the regular and the AltTester input by toggling the box with the `AltTester Input` label. Take into consideration that if you are using the New Input System, then after activating the AltTester input, you will only be able to interact with the instrumented build via your automated tests or the AltTester Desktop.
+    You can switch between the regular and the AltTester input by toggling the box with the `AltTester Input` label. Take into consideration that if you are using the New Input System, then after activating the AltTester input, you will only be able to interact with the instrumented build via your automated tests or the AltTester® Desktop.
 
 ```
 
@@ -228,7 +228,7 @@ Before running your tests you need to start the instrumented Unity application.
 
 ## Write and execute first test for your app
 
-To write tests with AltTester Unity SDK you need to import the AltDriver in your tests project.
+To write tests with AltTester® Unity SDK you need to import the AltDriver in your tests project.
 
 AltTester package contains AltDriver class used to connect to the instrumented app. In the setup method create an instance of the driver and in the tear-down method invoke the stop method of the driver. With the instance of the driver you can query the Unity objects and interact with the app.
 
@@ -244,7 +244,7 @@ AltTester package contains AltDriver class used to connect to the instrumented a
         2.  Right-click on Editor folder and select `Create -> AltTest`. This will create a template file in which you could start to write your test.
         3.  Name the file MyFirstTest.
         4.  Open AltTester Editor.
-        5.  Make sure that the AltTester Desktop app is running (Starting with version ``2.0.0``, AltTester Desktop must be running on your PC while the tests are running).
+        5.  Make sure that the AltTester® Desktop app is running (Starting with version ``2.0.0``, AltTester® Desktop must be running on your PC while the tests are running).
         6.  In the `Run Tests` section press "Run All Tests" button. You should see the output of the tests in Unity Editor Console
 
         Example test file:
@@ -280,12 +280,12 @@ AltTester package contains AltDriver class used to connect to the instrumented a
         **Prerequisite:**
             - `.NET <https://dotnet.microsoft.com/en-us/download>`_ installed.
             - Instrumented build.
-            - The AltTester Desktop installed on your PC.
+            - The AltTester® Desktop installed on your PC.
 
         **Connection:**
-            Starting with version ``2.0.0``, the AltTester Desktop must be running on your PC while the tests are running.
+            Starting with version ``2.0.0``, the AltTester® Desktop must be running on your PC while the tests are running.
 
-            1. The AltTester Desktop app is running.
+            1. The AltTester® Desktop app is running.
             2. The instrumented build is running.
             3. Configure the IP of the build in order to match the IP of the machine (PC) the Desktop app is running on.
             4. Then press the restart button in the AltTester dialog and wait until the `Connected to AltServer…` message is displayed in the dialog.
@@ -341,12 +341,12 @@ AltTester package contains AltDriver class used to connect to the instrumented a
         **Prerequisite:**
             - `Java <https://www.java.com/download/ie_manual.jsp>`_ installed.
             - Instrumented build.
-            - The AltTester Desktop installed on your PC.
+            - The AltTester® Desktop installed on your PC.
 
         **Connection:**
-            Starting with version ``2.0.0``, the AltTester Desktop must be running on your PC while the tests are running.
+            Starting with version ``2.0.0``, the AltTester® Desktop must be running on your PC while the tests are running.
 
-            1. The AltTester Desktop app is running.
+            1. The AltTester® Desktop app is running.
             2. The instrumented build is running.
             3. Configure the IP of the build in order to match the IP of the machine (PC) the Desktop app is running on.
             4. Then press the restart button in the AltTester dialog and wait until the `Connected to AltServer…` message is displayed in the dialog.
@@ -393,12 +393,12 @@ AltTester package contains AltDriver class used to connect to the instrumented a
         **Prerequisite:**
             - `Python <https://www.python.org/downloads/>`_ installed.
             - Instrumented build.
-            - The AltTester Desktop installed on your PC.
+            - The AltTester® Desktop installed on your PC.
 
         **Connection:**
-            Starting with version ``2.0.0``, the AltTester Desktop must be running on your PC while the tests are running.
+            Starting with version ``2.0.0``, the AltTester® Desktop must be running on your PC while the tests are running.
 
-            1. The AltTester Desktop app is running.
+            1. The AltTester® Desktop app is running.
             2. The instrumented build is running.
             3. Configure the IP of the build in order to match the IP of the machine (PC) the Desktop app is running on.
             4. Then press the restart button in the AltTester dialog and wait until the `Connected to AltServer…` message is displayed in the dialog.
diff --git a/Docs/source/pages/known-issues.rst b/Docs/source/pages/known-issues.rst
index e80297d87..b8bfc91c9 100644
--- a/Docs/source/pages/known-issues.rst
+++ b/Docs/source/pages/known-issues.rst
@@ -2,7 +2,7 @@
 Known Issues
 ============
 
-This section lists the known bugs and issues with the AltTester Unity SDK. If
+This section lists the known bugs and issues with the AltTester® Unity SDK. If
 available, we list a workaround to help troubleshoot the issue.
 
 To report a bug that isn't listed here, see our :doc:`contributing` section
@@ -28,7 +28,7 @@ Calling ``GetPNGScreenshot`` throws ``StackOverflow`` error (.NET Driver)
 .NET 5, or if you can't downgrade to .NET 5, try to run your tests with a lower
 resolution until this issue is fixed.
 
-**Affects**: AltUnity Tester v1.7.* and AltTester Unity SDK v1.8.* with .NET 6
+**Affects**: AltUnity Tester v1.7.* and AltTester® Unity SDK v1.8.* with .NET 6
 
 New Input System
 ----------------
@@ -40,7 +40,7 @@ Touch or Mouse actions do not work in tests
 Simulate Touch Input From Mouse or Pen is not checked and Lock Input to
 Game View is checked.
 
-**Affects**: AltUnity Tester v1.7.1, v1.7.2, AltTester Unity SDK v1.8.*, v2.0.0 and Input System with a version below 1.3.0
+**Affects**: AltUnity Tester v1.7.1, v1.7.2, AltTester® Unity SDK v1.8.*, v2.0.0 and Input System with a version below 1.3.0
 
 The PressKey command does not work
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -49,13 +49,13 @@ The PressKey command does not work
 ``wasPressedThisFrame`` and ``wasReleasedThisFrame*``. Use ``isPressed``
 instead.
 
-**Affects**: AltUnity Tester v1.7.1, v1.7.2, AltTester Unity SDK v1.8.*, v2.0.x
+**Affects**: AltUnity Tester v1.7.1, v1.7.2, AltTester® Unity SDK v1.8.*, v2.0.x
 
-Player Input is not working when connected to AltTester Unity SDK/Desktop
+Player Input is not working when connected to AltTester® Unity SDK/Desktop
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 **Problem**: Player Input is not working in the instrumented build when
-connected to the tests or to AltTester Desktop.
+connected to the tests or to AltTester® Desktop.
 
 **Affects**: All input actions created with the New Input System for app
 objects. The New Input System actions for UI objects are not affected, as well
@@ -71,7 +71,7 @@ Playing in Editor throws ``EntryPointNotFoundException: WebSocketSetOnOpen assem
 
 **Workaround**: Select a platform other than WebGL before Editor and if the error is still thrown while playing in Editor re-start de Unity project
 
-**Affects**: AltTester Unity SDK v2.0.x
+**Affects**: AltTester® Unity SDK v2.0.x
 
 Play in Editor does not start the instrumented app in the Unity Editor
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -80,7 +80,7 @@ Play in Editor does not start the instrumented app in the Unity Editor
 
 **Workaround**: Check the ``Keep ALTTESTER symbol defined`` box. Note that this problem does not occur when building an instrumented app for different platforms, only in the Editor.
 
-**Affects**: AltTester Unity SDK v1.8.*, AltTester Unity SDK v2.0.0
+**Affects**: AltTester® Unity SDK v1.8.*, AltTester® Unity SDK v2.0.0
 
 Opening AltTester Editor throws ``IndexOutOfRangeException: Index was outside the bounds of the array``
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -89,16 +89,16 @@ Opening AltTester Editor throws ``IndexOutOfRangeException: Index was outside th
 
 **Workaround**: Close and reopen the AltTester Editor window.
 
-**Affects**: AltTester Unity SDK v2.0.0, v2.0.1
+**Affects**: AltTester® Unity SDK v2.0.0, v2.0.1
 
 BlueStacks
 ----------
 
-Instrumented app with AltTester Unity SDK stops working in BlueStacks
+Instrumented app with AltTester® Unity SDK stops working in BlueStacks
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 **Workaround**: The issue seems to happen because of the communication protocol
-used inside the AltTester Unity SDK. There are other alternatives that work with
+used inside the AltTester® Unity SDK. There are other alternatives that work with
 instrumented builds. For Android you can use the Android Emulator inside the
 Android Studio. For iOS you can use a simulator inside Xcode.
 
@@ -108,9 +108,9 @@ Note: In version 2.0.2 this issue has been fixed.
 Networking
 ----------
 
-AltTester does not support proxy configurations
+AltTester® does not support proxy configurations
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-**Problem**: At the moment, AltTester does not have built-in support for proxy configurations. When using AltTester, the tool does not handle proxy settings, which can cause connectivity issues
+**Problem**: At the moment, AltTester® does not have built-in support for proxy configurations. When using AltTester®, the tool does not handle proxy settings, which can cause connectivity issues
 
-**Affects**: AltUnity Tester v1.7.1, v1.7.2, AltTester Unity SDK v1.8.*, v2.0.x
\ No newline at end of file
+**Affects**: AltUnity Tester v1.7.1, v1.7.2, AltTester® Unity SDK v1.8.*, v2.0.x
\ No newline at end of file
diff --git a/Docs/source/pages/license.rst b/Docs/source/pages/license.rst
index b3cd969d9..1952a8739 100644
--- a/Docs/source/pages/license.rst
+++ b/Docs/source/pages/license.rst
@@ -1,7 +1,7 @@
 License
 =======
 
-AltTester Unity SDK is licensed under the GNU General Public License v3.0. This
+AltTester® Unity SDK is licensed under the GNU General Public License v3.0. This
 means that the end user has the freedom to use, share and modify the software.
 It's a copyleft license, which means that if any derivative work must be
 distributed, it should be distributed under the same or equivalent license
@@ -13,9 +13,9 @@ company, without any obligations (no need to be copyright holders for the Unity
 engine).
 
 The only obligation you have regarding this open source software is related to
-distribution. If you want to distribute AltTester Unity SDK, or some parts of it
+distribution. If you want to distribute AltTester® Unity SDK, or some parts of it
 you have to make sure you distribute it under the same license terms. For
-example, if you plan to release a app containing AltTester Unity SDK, then you’d
+example, if you plan to release a app containing AltTester® Unity SDK, then you’d
 have to apply the same GPL3 terms to your app. Otherwise, if you only use it
 for developing and testing your app, you don't have any obligations.
 
diff --git a/Docs/source/pages/overview.md b/Docs/source/pages/overview.md
index 70311f524..98dab91ac 100644
--- a/Docs/source/pages/overview.md
+++ b/Docs/source/pages/overview.md
@@ -1,6 +1,6 @@
 # Overview
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your Unity application and interact with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your Unity application and interact with them using tests written in C#, Python or Java.
 
 You can run your tests on real devices (mobile, PCs, etc.) or inside the Unity Editor.
 
@@ -22,20 +22,20 @@ You can run your tests on real devices (mobile, PCs, etc.) or inside the Unity E
 
 ## How it works
 
-AltTester Unity SDK framework contains the following modules:
+AltTester® Unity SDK framework contains the following modules:
 
 * AltDriver
 * AltTester Package (Unity)
 * AltServer
 
 
-AltTester Unity SDK is used to instrument your Unity App to expose access to all the objects in the Unity hierarchy. The instrumented Unity App opens up a Web socket connection on the device running the Unity application and waits for an AltDriver to connect after starting the application.
+AltTester® Unity SDK is used to instrument your Unity App to expose access to all the objects in the Unity hierarchy. The instrumented Unity App opens up a Web socket connection on the device running the Unity application and waits for an AltDriver to connect after starting the application.
 
 AltDriver module is used to connect to the instrumented Unity App, access all the Unity objects and interact with them through tests written in C#, Java or Python.
 
 AltTester Package contains the AltTester Editor window which is the GUI used for instrumenting a Unity app and running C# tests directly from Unity Editor.
 
-The AltServer module is used to create the bridge between the tests and the instrumented Unity App. It acts as a websocket server that facilitates communication between AltDriver (tests) and AltTester Unity SDK (instrumented Unity App).
+The AltServer module is used to create the bridge between the tests and the instrumented Unity App. It acts as a websocket server that facilitates communication between AltDriver (tests) and AltTester® Unity SDK (instrumented Unity App).
 
 ![Architecture](../_static/img/overview/architecture1.png)
 ![Architecture](../_static/img/overview/architecture2.png)
diff --git a/Docs/source/pages/upgrade-guides.rst b/Docs/source/pages/upgrade-guides.rst
index c721e12bc..242b6174b 100644
--- a/Docs/source/pages/upgrade-guides.rst
+++ b/Docs/source/pages/upgrade-guides.rst
@@ -1,7 +1,7 @@
 Upgrade Guides
 ==============
 
-AltTester Unity SDK's major releases can include an upgrade guide to walk users through
+AltTester® Unity SDK's major releases can include an upgrade guide to walk users through
 backwards compatibility issues and changes to expect. See the navigation for
 the available upgrade guides.
 
diff --git a/Docs/source/pages/upgrade-guides/v-1-8-0.rst b/Docs/source/pages/upgrade-guides/v-1-8-0.rst
index 1ee1e679e..ea0a22edb 100644
--- a/Docs/source/pages/upgrade-guides/v-1-8-0.rst
+++ b/Docs/source/pages/upgrade-guides/v-1-8-0.rst
@@ -1,23 +1,23 @@
 Upgrade from v1.7.2 to v1.8.0
 =============================
 
-This guide will assist in upgrading your AltUnity projects from **v1.7.2** to AltTester Unity SDK **v1.8.0**.
+This guide will assist in upgrading your AltUnity projects from **v1.7.2** to AltTester® Unity SDK **v1.8.0**.
 
-AltUnity Tester becomes AltTester Unity SDK. The new one fits our mission to extend our test automation solution in the following directions:
+AltUnity Tester becomes AltTester® Unity SDK. The new one fits our mission to extend our test automation solution in the following directions:
 support new platforms, help game testers to start automation easier and start exploring how we could support Unreal and other engines.
 All changes are listed below, organized by drivers along with how to upgrade
-your code to work with AltTester Unity SDK v1.8.0.
+your code to work with AltTester® Unity SDK v1.8.0.
 
-To learn more about what's new in AltTester Unity SDK v1.8.0, read the
+To learn more about what's new in AltTester® Unity SDK v1.8.0, read the
 `v1.8.0 section from our changelog <https://github.com/alttester/AltTester-Unity-SDK/blob/development/CHANGELOG.md>`_.
 
 
 Unity
 -----
 
-To replace AltUnity Tester with AltTester Unity SDK you will need to do the following steps:
+To replace AltUnity Tester with AltTester® Unity SDK you will need to do the following steps:
 
-1. Download AltTester Unity SDK from :alttestersdkdownload:`our website <>`.
+1. Download AltTester® Unity SDK from :alttestersdkdownload:`our website <>`.
 2. Delete your AltUnity Tester folder
 3. Drag and drop the unitypackage you downloaded in step 1 to your Unity projects
 
diff --git a/README.md b/README.md
index 0b26069f7..d0eeba613 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
-# AltTester Unity SDK
+# AltTester® Unity SDK
 
-AltTester Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
+AltTester® Unity SDK is an open-source UI driven test automation tool that helps you find objects in your application and interacts with them using tests written in C#, Python or Java.
 
 ## Documentation
 


Test patch:
diff --git a/Bindings~/python/tests/integration/test_scene01.py b/Bindings~/python/tests/integration/test_scene01.py
index 5fe013e5f..ff38c7df8 100644
--- a/Bindings~/python/tests/integration/test_scene01.py
+++ b/Bindings~/python/tests/integration/test_scene01.py
@@ -788,7 +788,7 @@ def test_get_static_property(self):
             "UnityEngine.Screen", "SetResolution", "UnityEngine.CoreModule",
             parameters=["1920", "1080", "True"],
             type_of_parameters=["System.Int32",
-                                "System.Int32", "System.Boolean"],
+                                "System.Int32", "System.Boolean"]
         )
         width = self.altdriver.get_static_property(
             "UnityEngine.Screen", "currentResolution.width",
diff --git a/Docs/source/_static/img/alttester-editor/popup.png b/Docs/source/_static/img/alttester-editor/popup.png
index d315fc3a9..12cefb86f 100644
Binary files a/Docs/source/_static/img/alttester-editor/popup.png and b/Docs/source/_static/img/alttester-editor/popup.png differ
diff --git a/Docs/source/_static/img/get-started/downloading-importing-alttester-editor.png b/Docs/source/_static/img/get-started/downloading-importing-alttester-editor.png
index 3b3d1887b..04e144220 100644
Binary files a/Docs/source/_static/img/get-started/downloading-importing-alttester-editor.png and b/Docs/source/_static/img/get-started/downloading-importing-alttester-editor.png differ
diff --git a/Docs/source/pages/alttester-editor.md b/Docs/source/pages/alttester-editor.md
index 1cee4485b..d4ea45aa6 100644
--- a/Docs/source/pages/alttester-editor.md
+++ b/Docs/source/pages/alttester-editor.md
@@ -50,13 +50,13 @@ In the following sections you can see a breakdown of all the sections in the GUI
 
     If this option is checked, it will display the *"AltTester"* popup in
     app containing the text *"Waiting for connection on port 13000"*. That
-    means the build contains the AltTester Unity SDK. Popup will disappear once the
+    means the build contains the AltTester® Unity SDK. Popup will disappear once the
     tests are started.
     In case you modified the connection data inside the popup, you can use the *LeftCtrl+LeftShift+D+L* key combination to reset your connection data to the default values, a.k.a the values specified in the *Build Settings*.
 
 ![Popup Screenshot](../_static/img/alttester-editor/popup.png)
 
--   *Append "Test" to product name for AltTester Unity SDK builds*:
+-   *Append "Test" to product name for AltTester® Unity SDK builds*:
 
     Will add "Test" to the product name.
 
diff --git a/Docs/source/pages/alttester-with-appium.md b/Docs/source/pages/alttester-with-appium.md
index 1433c88f8..d6663f58f 100644
--- a/Docs/source/pages/alttester-with-appium.md
+++ b/Docs/source/pages/alttester-with-appium.md
@@ -13,14 +13,14 @@ No registration is needed and you can either download the latest version of the
 
 We've created an example python project which can be found [here](https://github.com/alttester-test-examples/Python-Android-with-Appium-AltTrashCat-) which hopefully can get you started on your own projects. Using it will also automatically install the requirements needed for running the tests. More details about it [below](#alttester-unity-sdk-with-appium-example).
 
-## Why use Appium together with AltTester Unity SDK
+## Why use Appium together with AltTester® Unity SDK
 
 There's a couple of reasons/scenarios for which you would want to use both of these frameworks:
 
--   By itself, AltTester Unity SDK cannot launch an app on a device. If you want to run tests in a pipeline, or by using [cloud services](./alttester-with-cloud), you can either create a script which will start your app, or you can use Appium before the tests execution;
--   AltTester Unity SDK cannot perform some types of actions, such as interacting with any native popups your app might have, or putting the app in the background and resuming it. In any of these cases you can use Appium to do the things that AltTester Unity SDK can't.
+-   By itself, AltTester® Unity SDK cannot launch an app on a device. If you want to run tests in a pipeline, or by using [cloud services](./alttester-with-cloud), you can either create a script which will start your app, or you can use Appium before the tests execution;
+-   AltTester® Unity SDK cannot perform some types of actions, such as interacting with any native popups your app might have, or putting the app in the background and resuming it. In any of these cases you can use Appium to do the things that AltTester® Unity SDK can't.
 
-## AltTester Unity SDK with Appium example
+## AltTester® Unity SDK with Appium example
 
 After you cloned our example project, there are a couple of things you need to check before running the tests:
 
@@ -43,9 +43,9 @@ After you cloned our example project, there are a couple of things you need to c
 The script will install any requirements that are missing from your machine (except Android SDK and XCode CLT), then run a basic test scenario:
 
 1. The app will be started by Appium;
-2. AltTester Unity SDK will ensure it's initially loaded;
+2. AltTester® Unity SDK will ensure it's initially loaded;
 3. Appium will put the app in the background for a couple of seconds, then resume it;
-4. AltTester Unity SDK will check if the app was resumed successfully.
+4. AltTester® Unity SDK will check if the app was resumed successfully.
 
 ```eval_rst
 .. note::
@@ -56,6 +56,6 @@ The script will install any requirements that are missing from your machine (exc
    
    2. Starting with **Selenium 4** the *DesiredCapabilities* are deprecated and the Webdriver now uses *Options* to pass capabilities, so if you're using Selenium 4, in order for the example project to work, you may have to update the code with the new setup - see the `Selenium documentation <https://www.selenium.dev/documentation/webdriver/getting_started/upgrade_to_selenium_4/>`_
    
-   3. The Appium driver needs to be created before the reverse port forwarding needed by AltTester Unity SDK is done. This is because Appium clears any other reverse port forwarding when it starts.
+   3. The Appium driver needs to be created before the reverse port forwarding needed by AltTester® Unity SDK is done. This is because Appium clears any other reverse port forwarding when it starts.
 
 ```