Merge branch 'develop' into kitsu-custom-commentfield

openpype/hosts/max/api/plugin.py

@@ -101,7 +101,9 @@ class MaxCreator(Creator, MaxCreatorBase):
             instance_node = rt.getNodeByName(
                 instance.data.get("instance_node"))
             if instance_node:
-                rt.delete(rt.getNodeByName(instance_node))
+                rt.select(instance_node)
+                rt.execute(f'for o in selection do for c in o.children do c.parent = undefined')    # noqa
+                rt.delete(instance_node)
 
             self._remove_instance_from_context(instance)
 

openpype/hosts/maya/api/customize.py

@@ -11,6 +11,7 @@ import maya.mel as mel
 from openpype import resources
 from openpype.tools.utils import host_tools
 from .lib import get_main_window
+from ..tools import show_look_assigner
 
 log = logging.getLogger(__name__)
 
@@ -112,7 +113,7 @@ def override_toolbox_ui():
             annotation="Look Manager",
             label="Look Manager",
             image=os.path.join(icons, "lookmanager.png"),
-            command=host_tools.show_look_assigner,
+            command=show_look_assigner,
             width=icon_size,
             height=icon_size,
             parent=parent

openpype/hosts/maya/api/menu.py

@@ -12,6 +12,7 @@ from openpype.pipeline.workfile import BuildWorkfile
 from openpype.tools.utils import host_tools
 from openpype.hosts.maya.api import lib, lib_rendersettings
 from .lib import get_main_window, IS_HEADLESS
+from ..tools import show_look_assigner
 
 from .workfile_template_builder import (
     create_placeholder,
@@ -139,7 +140,7 @@ def install():
 
         cmds.menuItem(
             "Look assigner...",
-            command=lambda *args: host_tools.show_look_assigner(
+            command=lambda *args: show_look_assigner(
                 parent_widget
             )
         )

openpype/hosts/maya/plugins/inventory/connect_geometry.py

@@ -134,7 +134,7 @@ class ConnectGeometry(InventoryAction):
             bool
         """
 
-        from Qt import QtWidgets
+        from qtpy import QtWidgets
 
         accept = QtWidgets.QMessageBox.Ok
         if show_cancel:

openpype/hosts/maya/plugins/inventory/connect_xgen.py

@@ -149,7 +149,7 @@ class ConnectXgen(InventoryAction):
             bool
         """
 
-        from Qt import QtWidgets
+        from qtpy import QtWidgets
 
         accept = QtWidgets.QMessageBox.Ok
         if show_cancel:

openpype/hosts/maya/plugins/load/load_arnold_standin.py

@@ -2,7 +2,6 @@ import os
 import clique
 
 import maya.cmds as cmds
-import mtoa.ui.arnoldmenu
 
 from openpype.settings import get_project_settings
 from openpype.pipeline import (
@@ -36,6 +35,11 @@ class ArnoldStandinLoader(load.LoaderPlugin):
     color = "orange"
 
     def load(self, context, name, namespace, options):
+
+        # Make sure to load arnold before importing `mtoa.ui.arnoldmenu`
+        cmds.loadPlugin("mtoa", quiet=True)
+        import mtoa.ui.arnoldmenu
+
         version = context['version']
         version_data = version.get("data", {})
 

openpype/hosts/maya/plugins/load/load_xgen.py

@@ -3,7 +3,7 @@ import os
 import maya.cmds as cmds
 import xgenm
 
-from Qt import QtWidgets
+from qtpy import QtWidgets
 
 import openpype.hosts.maya.api.plugin
 from openpype.hosts.maya.api.lib import (

openpype/hosts/maya/plugins/publish/collect_review.py

@@ -23,6 +23,9 @@ class CollectReview(pyblish.api.InstancePlugin):
 
         task = legacy_io.Session["AVALON_TASK"]
 
+        # Get panel.
+        instance.data["panel"] = cmds.playblast(activeEditor=True)
+
         # get cameras
         members = instance.data['setMembers']
         cameras = cmds.ls(members, long=True,

openpype/hosts/maya/plugins/publish/extract_playblast.py

@@ -118,7 +118,6 @@ class ExtractPlayblast(publish.Extractor):
 
         # Need to explicitly enable some viewport changes so the viewport is
         # refreshed ahead of playblasting.
-        panel = cmds.getPanel(withFocus=True)
         keys = [
             "useDefaultMaterial",
             "wireframeOnShaded",
@@ -129,10 +128,12 @@ class ExtractPlayblast(publish.Extractor):
         viewport_defaults = {}
         for key in keys:
             viewport_defaults[key] = cmds.modelEditor(
-                panel, query=True, **{key: True}
+                instance.data["panel"], query=True, **{key: True}
             )
             if preset["viewport_options"][key]:
-                cmds.modelEditor(panel, edit=True, **{key: True})
+                cmds.modelEditor(
+                    instance.data["panel"], edit=True, **{key: True}
+                )
 
         override_viewport_options = (
             capture_presets['Viewport Options']['override_viewport_options']
@@ -147,12 +148,10 @@ class ExtractPlayblast(publish.Extractor):
 
             # Update preset with current panel setting
             # if override_viewport_options is turned off
-            panel = cmds.getPanel(withFocus=True) or ""
-            if not override_viewport_options and "modelPanel" in panel:
-                panel_preset = capture.parse_active_view()
+            if not override_viewport_options:
+                panel_preset = capture.parse_view(instance.data["panel"])
                 panel_preset.pop("camera")
                 preset.update(panel_preset)
-                cmds.setFocus(panel)
 
             self.log.info(
                 "Using preset:\n{}".format(
@@ -163,7 +162,10 @@ class ExtractPlayblast(publish.Extractor):
             path = capture.capture(log=self.log, **preset)
 
         # Restoring viewport options.
-        cmds.modelEditor(panel, edit=True, **viewport_defaults)
+        if viewport_defaults:
+            cmds.modelEditor(
+                instance.data["panel"], edit=True, **viewport_defaults
+            )
 
         cmds.setAttr("{}.panZoomEnabled".format(preset["camera"]), pan_zoom)
 

openpype/hosts/maya/tools/__init__.py

@@ -0,0 +1,27 @@
+from openpype.tools.utils.host_tools import qt_app_context
+
+
+class MayaToolsSingleton:
+    _look_assigner = None
+
+
+def get_look_assigner_tool(parent):
+    """Create, cache and return look assigner tool window."""
+    if MayaToolsSingleton._look_assigner is None:
+        from .mayalookassigner import MayaLookAssignerWindow
+        mayalookassigner_window = MayaLookAssignerWindow(parent)
+        MayaToolsSingleton._look_assigner = mayalookassigner_window
+    return MayaToolsSingleton._look_assigner
+
+
+def show_look_assigner(parent=None):
+    """Look manager is Maya specific tool for look management."""
+
+    with qt_app_context():
+        look_assigner_tool = get_look_assigner_tool(parent)
+        look_assigner_tool.show()
+
+        # Pull window to the front.
+        look_assigner_tool.raise_()
+        look_assigner_tool.activateWindow()
+        look_assigner_tool.showNormal()

openpype/settings/entities/schemas/README.md

@@ -350,7 +350,7 @@ How output of the schema could look like on save:
 - number input, can be used for both integer and float
     - key `"decimal"` defines how many decimal places will be used, 0 is for integer input (Default: `0`)
     - key `"minimum"` as minimum allowed number to enter (Default: `-99999`)
-    - key `"maxium"` as maximum allowed number to enter (Default: `99999`)
+    - key `"maximum"` as maximum allowed number to enter (Default: `99999`)
 - key `"steps"` will change single step value of UI inputs (using arrows and wheel scroll)
 - for UI it is possible to show slider to enable this option set `show_slider` to `true`
 ```

openpype/tools/utils/host_tools.py

@@ -38,7 +38,6 @@ class HostToolsHelper:
         self._subset_manager_tool = None
         self._scene_inventory_tool = None
         self._library_loader_tool = None
-        self._look_assigner_tool = None
         self._experimental_tools_dialog = None
 
     @property
@@ -219,27 +218,6 @@ class HostToolsHelper:
 
         raise ImportError("No Pyblish GUI found")
 
-    def get_look_assigner_tool(self, parent):
-        """Create, cache and return look assigner tool window."""
-        if self._look_assigner_tool is None:
-            from openpype.tools.mayalookassigner import MayaLookAssignerWindow
-
-            mayalookassigner_window = MayaLookAssignerWindow(parent)
-            self._look_assigner_tool = mayalookassigner_window
-        return self._look_assigner_tool
-
-    def show_look_assigner(self, parent=None):
-        """Look manager is Maya specific tool for look management."""
-
-        with qt_app_context():
-            look_assigner_tool = self.get_look_assigner_tool(parent)
-            look_assigner_tool.show()
-
-            # Pull window to the front.
-            look_assigner_tool.raise_()
-            look_assigner_tool.activateWindow()
-            look_assigner_tool.showNormal()
-
     def get_experimental_tools_dialog(self, parent=None):
         """Dialog of experimental tools.
 
@@ -315,9 +293,6 @@ class HostToolsHelper:
         elif tool_name == "sceneinventory":
             return self.get_scene_inventory_tool(parent, *args, **kwargs)
 
-        elif tool_name == "lookassigner":
-            return self.get_look_assigner_tool(parent, *args, **kwargs)
-
         elif tool_name == "publish":
             self.log.info("Can't return publish tool window.")
 
@@ -356,9 +331,6 @@ class HostToolsHelper:
         elif tool_name == "sceneinventory":
             self.show_scene_inventory(parent, *args, **kwargs)
 
-        elif tool_name == "lookassigner":
-            self.show_look_assigner(parent, *args, **kwargs)
-
         elif tool_name == "publish":
             self.show_publish(parent, *args, **kwargs)
 
@@ -436,10 +408,6 @@ def show_scene_inventory(parent=None):
     _SingletonPoint.show_tool_by_name("sceneinventory", parent)
 
 
-def show_look_assigner(parent=None):
-    _SingletonPoint.show_tool_by_name("lookassigner", parent)
-
-
 def show_publish(parent=None):
     _SingletonPoint.show_tool_by_name("publish", parent)
 

website/docs/admin_environment.md

@@ -27,4 +27,4 @@ import TabItem from '@theme/TabItem';
 - for more details on how to use it go [here](admin_use#check-for-mongodb-database-connection)
 
 ## OPENPYPE_USERNAME
-- if set it overides system created username
+- if set it overrides system created username

website/docs/admin_hosts_maya.md

@@ -142,7 +142,7 @@ Fill in the necessary fields (the optional fields are regex filters)
 ![new place holder](assets/maya-placeholder_new.png)
 
 
-    - Builder type: Wether the the placeholder should load current asset representations or linked assets representations
+    - Builder type: Whether the the placeholder should load current asset representations or linked assets representations
 
     - Representation: Representation that will be loaded (ex: ma, abc, png, etc...)
 

website/docs/admin_settings.md

@@ -7,12 +7,15 @@ sidebar_label: Working with settings
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-OpenPype stores all of it's settings and configuration in the mongo database. To make the configuration as easy as possible we provide a robust GUI where you can access and change everything that is configurable
+OpenPype stores all of its settings and configuration in the mongo database. To make the configuration as easy as possible we provide a robust GUI where you can access and change everything that is configurable
 
 **Settings** GUI can be started from the tray menu *Admin -> Studio Settings*.
 
-Please keep in mind that these settings are set-up for the full studio and not per-individual. If you're looking for individual artist settings, you can head to
-[Local Settings](admin_settings_local.md) section in the artist documentation.
+:::important Studio Settings versus Local Settings
+Please keep in mind that these settings are set up for the full studio and not per-individual. If you're looking for individual artist settings, you can head to
+[Local Settings](admin_settings_local.md) section in the documentation.
+:::
+
 
 ## Categories
 
@@ -76,7 +79,7 @@ You can also reset any settings to OpenPype default by doing `right click` and `
 Many settings are useful to be adjusted on a per-project basis. To identify project
 overrides, they are marked with **orange edge** and **orange labels** in the settings GUI.
 
-The process of settting project overrides is similar to setting the Studio defaults. The key difference is to select a particular project you want to be configure. Those projects can be found on the left hand side of the Project Settings tab.
+The process of setting project overrides is similar to setting the Studio defaults. The key difference is to select a particular project you want to be configure. Those projects can be found on the left hand side of the Project Settings tab.
 
 In the image below you can see all three overrides at the same time.
 1. Deadline has **no changes to the OpenPype defaults** at all — **grey** colour of left bar.

website/docs/admin_use.md

@@ -68,7 +68,7 @@ Add `--headless` to run OpenPype without graphical UI (useful on server or on au
 
 `--verbose` `<level>` - change log verbose level of OpenPype loggers.
 
-Level value can be integer in range `0-50` or one of enum strings `"notset" (0)`, `"debug" (10)`, `"info" (20)`, `"warning" (30)`, `"error" (40)`, `"ciritcal" (50)`. Value is stored to `OPENPYPE_LOG_LEVEL` environment variable for next processes.
+Level value can be integer in range `0-50` or one of enum strings `"notset" (0)`, `"debug" (10)`, `"info" (20)`, `"warning" (30)`, `"error" (40)`, `"critical" (50)`. Value is stored to `OPENPYPE_LOG_LEVEL` environment variable for next processes.
 
 ```shell
 openpype_console --verbose debug

website/docs/artist_hosts_3dsmax.md

@@ -47,7 +47,7 @@ This is the core functional area for you as a user. Most of your actions will ta
 ![Menu OpenPype](assets/3dsmax_menu_first_OP.png)
 
 :::note OpenPype Menu
-User should use this menu exclusively for **Opening/Saving** when dealing with work files not standard ```File Menu``` even though user still being able perform file operations via this menu but prefferably just performing quick saves during work session not saving actual workfile versions.
+User should use this menu exclusively for **Opening/Saving** when dealing with work files not standard ```File Menu``` even though user still being able perform file operations via this menu but preferably just performing quick saves during work session not saving actual workfile versions.
 :::
 
 ## Working With Scene Files
@@ -73,7 +73,7 @@ OpenPype correctly names it and add version to the workfile. This basically happ
 
  etc. 
 
-Basically meaning user is free of guessing what is the correct naming and other neccessities to keep everthing in order and managed.
+Basically meaning user is free of guessing what is the correct naming and other necessities to keep everything in order and managed.
 
 > Note: user still has also other options for naming like ```Subversion```, ```Artist's Note``` but we won't dive into those now.
 

website/docs/artist_hosts_aftereffects.md

@@ -34,7 +34,7 @@ a correct name. You should use it instead of standard file saving dialog.
 
 In AfterEffects you'll find the tools in the `OpenPype` extension:
 
-![Extension](assets/photoshop_extension.PNG) <!-- same menu as in PS -->
+![Extension](assets/photoshop_extension.png) <!-- same menu as in PS -->
 
 You can show the extension panel by going to `Window` > `Extensions` > `OpenPype`.
 
@@ -104,7 +104,7 @@ There are currently 2 options of `render` item:
 
 When you want to load existing published work, you can use the `Loader` tool. You can reach it in the extension's panel.
 
-![Loader](assets/photoshop_loader.PNG) <!-- picture needs to be changed -->
+![Loader](assets/photoshop_loader.png) <!-- picture needs to be changed -->
 
 The supported families for loading into AfterEffects are:
 
@@ -128,7 +128,7 @@ Now that we have some content loaded, you can manage which version is loaded. Th
 Loaded images have to stay as smart layers in order to be updated. If you rasterize the layer, you can no longer update it to a different version using OpenPype tools.
 :::
 
-![Loader](assets/photoshop_manage.PNG)
+![Loader](assets/photoshop_manage.png)
 
 You can switch to a previous version of the image or update to the latest.
 

website/docs/artist_hosts_harmony.md

@@ -44,7 +44,7 @@ Because the saving to the network location happens in the background, be careful
 
 `OpenPype > Create`
 
-![Creator](assets/harmony_creator.PNG)
+![Creator](assets/harmony_creator.png)
 
 These are the families supported in Harmony:
 

website/docs/artist_hosts_hiero.md

@@ -231,14 +231,14 @@ All published instances that will replace the place holder must contain unique i
 ![Create menu](assets/nuke_publishedinstance.png)
 
 
-The informations about these objects are given by the user by filling the extra attributes of the Place Holder
+The information about these objects are given by the user by filling the extra attributes of the Place Holder
 
 ![Create menu](assets/nuke_fillingExtraAttributes.png)
 
 
 
 ### Update Place Holder
-This tool alows the user to change the information provided in the extra attributes of the selected Place Holder.
+This tool allows the user to change the information provided in the extra attributes of the selected Place Holder.
 
 ![Create menu](assets/nuke_updatePlaceHolder.png)
 
@@ -250,7 +250,7 @@ This tool imports the template used and replaces the existed PlaceHolders with t
 ![Create menu](assets/nuke_buildWorfileFromTemplate.png)
 
 #### Result
-- Replace `PLACEHOLDER` node in the template with the published instance corresponding to the informations provided in extra attributes of the Place Holder
+- Replace `PLACEHOLDER` node in the template with the published instance corresponding to the information provided in extra attributes of the Place Holder
 
 ![Create menu](assets/nuke_buildworkfile.png)
 

website/docs/artist_hosts_photoshop.md

@@ -75,7 +75,7 @@ enabled instances, you could see more information after clicking on `Details` ta
 
 ![Image instances creates](assets/photoshop_publish_validations.png)
 
-In this dialog you could see publishable instances in left colummn, triggered plugins in the middle and logs in the right column.
+In this dialog you could see publishable instances in left column, triggered plugins in the middle and logs in the right column.
 
 In left column you could see that `review` instance was created automatically. This instance flattens all publishable instances or
 all visible layers if no publishable instances were created into single image which could serve as a single reviewable element (for example in Ftrack).

website/docs/artist_tools_sync_queu.md

@@ -2,7 +2,7 @@
 id: artist_tools_sync_queue
 title: Sync Queue
 sidebar_label: Sync Queue
-description: Track sites syncronization progress.
+description: Track sites synchronization progress.
 ---
 
 # Sync Queue

website/docs/dev_colorspace.md

@@ -24,8 +24,8 @@ It's up to the Loaders to read these values and apply the correct expected color
 ### Keys
 - **colorspace** - string value used in other publish plugins and loaders
 - **config** - storing two versions of path.
-  - **path** - is formated and with baked platform root. It is used for posible need to find out where we were sourcing color config during publishing.
-  - **template** - unformated tempate resolved from settings. It is used for other plugins targeted to remote publish which could be processed at different platform.
+  - **path** - is formatted and with baked platform root. It is used for possible need to find out where we were sourcing color config during publishing.
+  - **template** - unformatted template resolved from settings. It is used for other plugins targeted to remote publish which could be processed at different platform.
 
 ### Example
     {

website/docs/dev_host_implementation.md

@@ -45,10 +45,10 @@ openpype/hosts/{host name}
 ```
 
 ### Launch Hooks
-Launch hooks are not directly connected to host implementation, but they can be used to modify launch of process which may be crutial for the implementation. Launch hook are plugins called when DCC is launched. They are processed in sequence before and after launch. Pre launch hooks can change how process of DCC is launched, e.g. change subprocess flags, modify environments or modify launch arguments. If prelaunch hook crashes the application is not launched at all. Postlaunch hooks are triggered after launch of subprocess. They can be used to change statuses in your project tracker, start timer, etc. Crashed postlaunch hooks have no effect on rest of postlaunch hooks or launched process. They can be filtered by platform, host and application and order is defined by integer value. Hooks inside host are automatically loaded (one reason why folder name should match host name) or can be defined from modules. Hooks execution share same launch context where can be stored data used across multiple hooks (please be very specific in stored keys e.g. 'project' vs. 'project_name'). For more detailed information look into `openpype/lib/applications.py`.
+Launch hooks are not directly connected to host implementation, but they can be used to modify launch of process which may be crucial for the implementation. Launch hook are plugins called when DCC is launched. They are processed in sequence before and after launch. Pre launch hooks can change how process of DCC is launched, e.g. change subprocess flags, modify environments or modify launch arguments. If prelaunch hook crashes the application is not launched at all. Postlaunch hooks are triggered after launch of subprocess. They can be used to change statuses in your project tracker, start timer, etc. Crashed postlaunch hooks have no effect on rest of postlaunch hooks or launched process. They can be filtered by platform, host and application and order is defined by integer value. Hooks inside host are automatically loaded (one reason why folder name should match host name) or can be defined from modules. Hooks execution share same launch context where can be stored data used across multiple hooks (please be very specific in stored keys e.g. 'project' vs. 'project_name'). For more detailed information look into `openpype/lib/applications.py`.
 
 ### Public interface
-Public face is at this moment related to launching of the DCC. At this moment there there is only option to modify environment variables before launch by implementing function `add_implementation_envs` (must be available in `openpype/hosts/{host name}/__init__.py`). The function is called after pre launch hooks, as last step before subprocess launch, to be able set environment variables crutial for proper integration. It is also good place for functions that are used in prelaunch hooks and in-DCC integration. Future plans are to be able get workfiles extensions from here. Right now workfiles extensions are hardcoded in `openpype/pipeline/constants.py` under `HOST_WORKFILE_EXTENSIONS`, we would like to handle hosts as addons similar to OpenPype modules, and more improvements which are now hardcoded.
+Public face is at this moment related to launching of the DCC. At this moment there there is only option to modify environment variables before launch by implementing function `add_implementation_envs` (must be available in `openpype/hosts/{host name}/__init__.py`). The function is called after pre launch hooks, as last step before subprocess launch, to be able set environment variables crucial for proper integration. It is also good place for functions that are used in prelaunch hooks and in-DCC integration. Future plans are to be able get workfiles extensions from here. Right now workfiles extensions are hardcoded in `openpype/pipeline/constants.py` under `HOST_WORKFILE_EXTENSIONS`, we would like to handle hosts as addons similar to OpenPype modules, and more improvements which are now hardcoded.
 
 ### Integration
 We've prepared base class `HostBase` in `openpype/host/host.py` to define minimum requirements and provide some default method implementations. The minimum requirement for a host is `name` attribute, this host would not be able to do much but is valid. To extend functionality we've prepared interfaces that helps to identify what is host capable of and if is possible to use certain tools with it. For those cases we defined interfaces for each workflow. `IWorkfileHost` interface add requirement to implement workfiles related methods which makes host usable in combination with Workfiles tool. `ILoadHost` interface add requirements to be able load, update, switch or remove referenced representations which should add support to use Loader and Scene Inventory tools. `INewPublisher` interface is required to be able use host with new OpenPype publish workflow. This is what must or can be implemented to allow certain functionality. `HostBase` will have more responsibility which will be taken from global variables in future. This process won't happen at once, but will be slow to keep backwards compatibility for some time.

website/docs/dev_publishing.md

@@ -415,7 +415,7 @@ class CreateRender(Creator):
         #    - 'asset' - asset name
         #    - 'task' - task name
         #    - 'variant' - variant
-        #    - 'family' - instnace family
+        #    - 'family' - instance family
 
         # Check if should use selection or not
         if pre_create_data.get("use_selection"):

website/docs/dev_settings.md

@@ -355,7 +355,7 @@ These inputs wraps another inputs into {key: value} relation
                 {
                     "type": "text",
                     "key": "command",
-                    "label": "Comand"
+                    "label": "Command"
                 }
             ]
         },
@@ -420,7 +420,7 @@ How output of the schema could look like on save:
 - number input, can be used for both integer and float
     - key `"decimal"` defines how many decimal places will be used, 0 is for integer input (Default: `0`)
     - key `"minimum"` as minimum allowed number to enter (Default: `-99999`)
-    - key `"maxium"` as maximum allowed number to enter (Default: `99999`)
+    - key `"maximum"` as maximum allowed number to enter (Default: `99999`)
 - key `"steps"` will change single step value of UI inputs (using arrows and wheel scroll)
 - for UI it is possible to show slider to enable this option set `show_slider` to `true`
 ```javascript
@@ -602,7 +602,7 @@ How output of the schema could look like on save:
 - there are 2 possible ways how to set the type:
     1.) dictionary with item modifiers (`number` input has `minimum`, `maximum` and `decimals`) in that case item type must be set as value of `"type"` (example below)
     2.) item type name as string without modifiers (e.g. [text](#text))
-    3.) enhancement of 1.) there is also support of `template` type but be carefull about endless loop of templates
+    3.) enhancement of 1.) there is also support of `template` type but be careful about endless loop of templates
         - goal of using `template` is to easily change same item definitions in multiple lists
 
 1.) with item modifiers

website/docs/dev_testing.md

@@ -57,7 +57,7 @@ Content:
 
 Contains end to end testing in a DCC. Currently it is setup to start DCC application with prepared worfkile, run publish process and compare results in DB and file system automatically.
 This approach is implemented as it should work in any DCC application and should cover most common use cases. Not all hosts allow "real headless" publishing, but all hosts should allow to trigger 
-publish process programatically when UI of host is actually running.
+publish process programmatically when UI of host is actually running.
 
 There will be eventually also possibility to build workfile and publish it programmatically, this would work only in DCCs that support it (Maya, Nuke).
 

website/docs/manager_ftrack.md

@@ -4,7 +4,7 @@ title: Ftrack
 sidebar_label: Project Manager
 ---
 
-Ftrack is currently the main project management option for OpenPype. This documentation assumes that you are familiar with Ftrack and it's basic principles. If you're new to Ftrack, we recommend having a thorough look at [Ftrack Official Documentation](https://help.ftrack.com/en/).
+Ftrack is currently the main project management option for OpenPype. This documentation assumes that you are familiar with Ftrack and its basic principles. If you're new to Ftrack, we recommend having a thorough look at [Ftrack Official Documentation](https://help.ftrack.com/en/).
 
 ## Project management
 Setting project attributes is the key to properly working pipeline.

website/docs/module_ftrack.md

@@ -8,7 +8,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 
-Ftrack is currently the main project management option for OpenPype. This documentation assumes that you are familiar with Ftrack and it's basic principles. If you're new to Ftrack, we recommend having a thorough look at [Ftrack Official Documentation](http://ftrack.rtd.ftrack.com/en/stable/).
+Ftrack is currently the main project management option for OpenPype. This documentation assumes that you are familiar with Ftrack and its basic principles. If you're new to Ftrack, we recommend having a thorough look at [Ftrack Official Documentation](http://ftrack.rtd.ftrack.com/en/stable/).
 
 ## Prepare Ftrack for OpenPype
 

website/docs/module_kitsu.md

@@ -7,7 +7,7 @@ sidebar_label: Kitsu
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-Kitsu is a great open source production tracker and can be used for project management instead of Ftrack. This documentation assumes that you are familiar with Kitsu and it's basic principles. If you're new to Kitsu, we recommend having a thorough look at [Kitsu Official Documentation](https://kitsu.cg-wire.com/).
+Kitsu is a great open source production tracker and can be used for project management instead of Ftrack. This documentation assumes that you are familiar with Kitsu and its basic principles. If you're new to Kitsu, we recommend having a thorough look at [Kitsu Official Documentation](https://kitsu.cg-wire.com/).
 
 ## Prepare Kitsu for OpenPype
 
@@ -41,4 +41,4 @@ openpype_console module kitsu push-to-zou -l me@domain.ext -p my_password
 ## Q&A
 ### Is it safe to rename an entity from Kitsu?
 Absolutely! Entities are linked by their unique IDs between the two databases.  
-But renaming from the OP's Project Manager won't apply the change to Kitsu, it'll be overriden during the next synchronization.
+But renaming from the OP's Project Manager won't apply the change to Kitsu, it'll be overridden during the next synchronization.

website/docs/module_site_sync.md

@@ -89,7 +89,7 @@ all share the same provider).
 
 Handles files stored on disk storage.
 
-Local drive provider is the most basic one that is used for accessing all standard hard disk storage scenarios. It will work with any storage that can be mounted on your system in a standard way. This could correspond to a physical external hard drive, network mounted storage, internal drive or even VPN connected network drive. It doesn't care about how te drive is mounted, but you must be able to point to it with a simple directory path.
+Local drive provider is the most basic one that is used for accessing all standard hard disk storage scenarios. It will work with any storage that can be mounted on your system in a standard way. This could correspond to a physical external hard drive, network mounted storage, internal drive or even VPN connected network drive. It doesn't care about how the drive is mounted, but you must be able to point to it with a simple directory path.
 
 Default sites `local` and `studio` both use local drive provider.
 

website/docs/project_settings/settings_project_global.md

@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 Project settings can have project specific values. Each new project is using studio values defined in **default** project but these values can be modified or overridden per project.
 
 :::warning Default studio values
-Projects always use default project values unless they have [project override](../admin_settings#project-overrides) (orage colour). Any changes in default project may affect all existing projects.
+Projects always use default project values unless they have [project override](../admin_settings#project-overrides) (orange colour). Any changes in default project may affect all existing projects.
 :::
 
 ## Color Management (ImageIO)
@@ -39,14 +39,14 @@ Procedure of resolving path (from above example) will look first into path 1st a
 ### Using File rules
 File rules are inspired by [OCIO v2 configuration]((https://opencolorio.readthedocs.io/en/latest/guides/authoring/rules.html)). Each rule has a unique name which can be overridden by host-specific _File rules_ (example: `project_settings/nuke/imageio/file_rules/rules`).
 
-The _input pattern_ matching uses REGEX expression syntax (try [regexr.com](https://regexr.com/)). Matching rules procedure's intention is to be used during publishing or loading of representation. Since the publishing procedure is run before integrator formate publish template path, make sure the pattern is working or any work render path.
+The _input pattern_ matching uses REGEX expression syntax (try [regexr.com](https://regexr.com/)). Matching rules procedure's intention is to be used during publishing or loading of representation. Since the publishing procedure is run before integrator format publish template path, make sure the pattern is working or any work render path.
 
 :::warning Colorspace name input
 The **colorspace name** value is a raw string input and no validation is run after saving project settings. We recommend to open the specified `config.ocio` file and copy pasting the exact colorspace names.
 :::
 
 ### Extract OIIO Transcode
-OIIOTools transcoder plugin with configurable output presets. Any incoming representation with `colorspaceData` is convertable to single or multiple representations with different target colorspaces or display and viewer names found in linked **config.ocio** file.
+OIIOTools transcoder plugin with configurable output presets. Any incoming representation with `colorspaceData` is convertible to single or multiple representations with different target colorspaces or display and viewer names found in linked **config.ocio** file.
 
 `oiiotool` is used for transcoding, eg. `oiiotool` must be present in `vendor/bin/oiio` or environment variable `OPENPYPE_OIIO_PATHS` must be provided for custom oiio installation.
 

website/docs/project_settings/settings_project_nuke.md

@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 Project settings can have project specific values. Each new project is using studio values defined in **default** project but these values can be modified or overridden per project.
 
 :::warning Default studio values
-Projects always use default project values unless they have [project override](../admin_settings#project-overrides) (orage colour). Any changes in default project may affect all existing projects.
+Projects always use default project values unless they have [project override](../admin_settings#project-overrides) (orange colour). Any changes in default project may affect all existing projects.
 :::
 
 ## Workfile Builder

website/docs/project_settings/settings_project_standalone.md

@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 Project settings can have project specific values. Each new project is using studio values defined in **default** project but these values can be modified or overridden per project.
 
 :::warning Default studio values
-Projects always use default project values unless they have [project override](../admin_settings#project-overrides) (orage colour). Any changes in default project may affect all existing projects.
+Projects always use default project values unless they have [project override](../admin_settings#project-overrides) (orange colour). Any changes in default project may affect all existing projects.
 :::
 
 ## Creator Plugins

website/docs/pype2/admin_ftrack.md

@@ -8,7 +8,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 
-Ftrack is currently the main project management option for Pype. This documentation assumes that you are familiar with Ftrack and it's basic principles. If you're new to Ftrack, we recommend having a thorough look at [Ftrack Official Documentation](http://ftrack.rtd.ftrack.com/en/stable/).
+Ftrack is currently the main project management option for Pype. This documentation assumes that you are familiar with Ftrack and its basic principles. If you're new to Ftrack, we recommend having a thorough look at [Ftrack Official Documentation](http://ftrack.rtd.ftrack.com/en/stable/).
 
 ## Prepare Ftrack for Pype
 

website/docs/system_introduction.md

@@ -15,9 +15,9 @@ various usage scenarios.
 
 ## Studio Preparation
 
-You can find detailed breakdown of technical requirements [here](dev_requirements), but in general OpenPype should be able
+You can find a detailed breakdown of technical requirements [here](dev_requirements), but in general OpenPype should be able
 to operate in most studios fairly quickly. The main obstacles are usually related to workflows and habits, that
-might not be fully compatible with what OpenPype is expecting or enforcing. It is recommended to go through artists [key concepts](artist_concepts) to get idea about basics.
+might not be fully compatible with what OpenPype is expecting or enforcing. It is recommended to go through artists [key concepts](artist_concepts) to get comfortable with the basics.
 
 Keep in mind that if you run into any workflows that are not supported, it's usually just because we haven't hit 
 that particular case and it can most likely be added upon request.