%YAML 1.1
%TAG !u! tag:unity3d.com,2011:
--- !u!114 &11400000
MonoBehaviour:
  m_ObjectHideFlags: 0
  m_CorrespondingSourceObject: {fileID: 0}
  m_PrefabInstance: {fileID: 0}
  m_PrefabAsset: {fileID: 0}
  m_GameObject: {fileID: 0}
  m_Enabled: 1
  m_EditorHideFlags: 0
  m_Script: {fileID: 11500000, guid: d813ff809ae82f643bf975031305d541, type: 3}
  m_Name: Check Documentation
  m_EditorClassIdentifier: 
  HasBeenInitialized: 1
  Id: 6
  Title: Check Documentation
  Description: If your asset contains any code (scripts, shaders) - we ask that you
    include offline documentation in the format of pdf or rtf with your submission,
    as it is mandatory for all packages that include scripts or other components
    that require set up. Your documentation must be organized with a table of contents
    and numbered, written in English and have no grammar mistakes. Create a setup
    guide with a step-by-step tutorial (pdf or video), as well as a script reference
    if users will need to do any coding. If your asset contains art (3D models, sprites)
    and you used code to set up a demo scene, you may skip this step.
  CategoryInfo:
    IsFailFilter: 1
    IsInclusiveFilter: 1
    AppliesToSubCategories: 1
    Filter: []
  ValidationType: 1
  TestScript: {fileID: 11500000, guid: 3c8425198983eda4c9b35aa0d59ea33c, type: 3}
