Bug fix - updated document for content field of vault oci_vault_secret

Author: sagarp337

website/docs/r/vault_secret.html.markdown

@@ -22,9 +22,9 @@ resource "oci_vault_secret" "test_secret" {
 	secret_content {
 		#Required
 		content_type = var.secret_secret_content_content_type
+		content = var.secret_secret_content_content		
 
 		#Optional
-		content = var.secret_secret_content_content
 		name = var.secret_secret_content_name
 		stage = var.secret_secret_content_stage
 	}
@@ -61,7 +61,7 @@ The following arguments are supported:
 * `key_id` - (Optional) The OCID of the master encryption key that is used to encrypt the secret.
 * `metadata` - (Optional) (Updatable) Additional metadata that you can use to provide context about how to use the secret during rotation or other administrative tasks. For example, for a secret that you use to connect to a database, the additional metadata might specify the connection endpoint and the connection string. Provide additional metadata as key-value pairs. 
 * `secret_content` - (Required) (Updatable) The content of the secret and metadata to help identify it.
-	* `content` - (Optional) (Updatable) The base64-encoded content of the secret.
+	* `content` - (Required) (Updatable) The base64-encoded content of the secret.
 	* `content_type` - (Required) (Updatable) content type . Example `BASE64` .
 	* `name` - (Optional) (Updatable) Names should be unique within a secret. Valid characters are uppercase or lowercase letters, numbers, hyphens, underscores, and periods.
 	* `stage` - (Optional) (Updatable) The rotation state of the secret content. The default is `CURRENT`, meaning that the secret is currently in use. A secret version that you mark as `PENDING` is staged and available for use, but you don't yet want to rotate it into current, active use. For example, you might create or update a secret and mark its rotation state as `PENDING` if you haven't yet updated the secret on the target system. When creating a secret, only the value `CURRENT` is applicable, although the value `LATEST` is also automatically applied. When updating  a secret, you can specify a version's rotation state as either `CURRENT` or `PENDING`.