GA of Attestations and Unknown

Author: kenieva

articles/governance/policy/concepts/attestation-structure.md

@@ -11,7 +11,7 @@ author: davidsmatlak
 Attestations are used by Azure Policy to set compliance states of resources or scopes targeted by [manual policies](effects.md#manual). They also allow users to provide additional metadata or link to evidence which accompanies the attested compliance state.  
 
 > [!NOTE]
-> Attestations are available only through the [Azure Resource Manager (ARM) API](/rest/api/policy/attestations).
+> Attestations can be created and managed only through Azure Policy [Azure Resource Manager (ARM) API](/rest/api/policy/attestations), [PowerShell](/powershell/module/az.policyinsights) or [Azure CLI](/cli/azure/policy/attestation). 
 
 ## Best practices
 

articles/governance/policy/concepts/compliance-states.md

@@ -55,7 +55,7 @@ An applicable resource has a compliance state of exempt for a policy assignment
 > [!NOTE]
 > _Exempt_ is different than _excluded_. For more details, see [scope](./scope.md).
 
-### Unknown (preview)
+### Unknown
 
  Unknown is the default compliance state for definitions with `manual` effect, unless the default has been explicitly set to compliant or non-compliant. This state indicates that an [attestation](./attestation-structure.md) of compliance is warranted. This compliance state only occurs for policy assignments with `manual` effect.