Updated versions and copyright dates

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2021 Indigo Domotics
+Copyright (c) 2024 Indigo Domotics
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,28 +1,29 @@
 # IndigoSDK
+
 Indigo includes a Python-based API and object model for integrating 3rd party hardware, applications, and services into 
 the Indigo Server. Indigo Plugins allow new native devices, triggers, and actions to be added directly to Indigo. The 
 latest [extensive technical documentation](https://www.indigodomo.com/docs/documents#technical_documents) is available online, including:
 
 - [Indigo Scripting Tutorial](https://www.indigodomo.com/docs/plugin_scripting_tutorial) - dive into scripting Indigo by examples.
-- [Indigo 2023.1 Plugin Developer's Guide](https://www.indigodomo.com/docs/plugin_guide) - how to create plugin bundles for easy distribution, plugin UI, APIs, 
+- [Indigo 2023.2 Plugin Developer's Guide](https://www.indigodomo.com/docs/plugin_guide) - how to create plugin bundles for easy distribution, plugin UI, APIs, 
   callback hooks, and more.
 - [Indigo Object Model Reference](https://www.indigodomo.com/docs/object_model_reference) - the Indigo Object Model (IOM) and how to use it in Python.
 
-### Plugins Examples
-Several Indigo Plugin examples are included in the SDK. These examples include the full python source code and XML 
+**Plugins Examples**
+Several Indigo Plugin examples are included in this SDK. These examples include the full python source code and XML 
 files. To see all the source files once downloaded to your Mac, right-click (or control-click) on the plugin bundle 
 (.indigoPlugin file) and select **Show Package Contents** menu item. The [Plugin Developer's Guide](https://www.indigodomo.com/docs/plugin_guide) has thorough 
 documentation on how each file is used.
 
-> [!NOTE]
-> **IMPORTANT:** Although these example plugins are great templates to start with, and we encourage you to copy them, 
+**IMPORTANT:** Although these example plugins are great templates to start with, and we encourage you to copy them, 
 you must edit the **Info.plist** file inside the bundle after you make a copy for your plugin. Inside the 
-**Info.plist** XML file you must give the plugin a unique identifier, called the `CFBundleIndentifier`. You should 
+**Info.plist** XML file you must give the plugin a unique identifier, called the `CFBundleIndentifier`. And you should 
 also change your plugin's display name (`CFBundleDisplayName`) and help URL (`CFBundleURLTypes`). See the 
 [Info.plist section of the Developer's Guide](https://www.indigodomo.com/docs/plugin_guide#the_infoplist_file) for additional details.
 
-### Development Support
+**Development Support**
+
 For help with plugin development, or to report any API problems or requests, join us on our 
 [active and helpful developer forum.](https://forums.indigodomo.com/viewforum.php?f=18)
 
-Copyright © 2023 Perceptive Automation, LLC. All rights reserved.
+Copyright © 2024 Perceptive Automation, LLC. All rights reserved.

Updating to API version 3.0 (Python 3).md

@@ -1,4 +1,4 @@
-**Updating to API version 3.0 (Python 3)** - random things we've run across and definitely not exhaustive
+**Updating to API version 3.0+ (Python 3)** - random things we've run across and definitely not exhaustive
 - `imports` implicit imports are no longer honored in the way they were in Python 2. 
   Python [PEP 328](https://peps.python.org/pep-0328/) explains the issues with implicit (relative) imports. 
   See also [Package Relative Imports](https://docs.python.org/3/reference/import.html#package-relative-imports)