diff --git a/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2.yml b/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2.yml
index e90a1d52fbe3..9a68698812ea 100644
--- a/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2.yml
+++ b/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2.yml
@@ -71,7 +71,7 @@ configuration:
   name: url
   required: true
   type: 0
-- display: Username / API Key (see '?')
+- display: Username / API Key
   name: credentials
   required: false
   type: 9
diff --git a/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2_description.md b/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2_description.md
index a84d2a0dfbff..aa3739a8d187 100644
--- a/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2_description.md
+++ b/Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2_description.md
@@ -1,9 +1,9 @@
 ### Using API Token authentication
-In order to use the integration with an API token you'll first need to change the `Username / API Key (see '?')` field to `_api_token_key`. Following this step, you can now enter the API Token into the `Password` field - this value will be used as an API key.
+In order to use the integration with an API token you'll first need to change the `Username / API Key` field to `_api_token_key`. Following this step, you can now enter the API Token into the `Password` field - this value will be used as an API key.
 
 
 ### Using custom authentication header
-In case the TAXII 2 server you're trying to connect to requires a custom authentication header, you'll first need to change the `Username / API Key (see '?')` field to `_header:` and the custom header name, e.g. `_header:custom_auth`. Following this step, you can now enter the custom authentication header value into the `Password` field - this value will be used as a custom authentication header.
+In case the TAXII 2 server you're trying to connect to requires a custom authentication header, you'll first need to change the `Username / API Key` field to `_header:` and the custom header name, e.g. `_header:custom_auth`. Following this step, you can now enter the custom authentication header value into the `Password` field - this value will be used as a custom authentication header.
 
 ### Complex Observation Mode
 Two or more Observation Expressions MAY be combined using a complex observation operator such as "AND", "OR", and "FOLLOWEDBY", e.g. `[ IP = 'b' ] AND [ URL = 'd' ]`. These relationships are not represented in CORTEX XSOAR threat intel management indicators. You can opt to create them while ignoring these relations, or you can opt to ignore these expressions - if you choose to ignore these expressions, then no indicators will be created for complex observations.
diff --git a/Packs/FeedTAXII/ReleaseNotes/1_1_9.md b/Packs/FeedTAXII/ReleaseNotes/1_1_9.md
new file mode 100644
index 000000000000..383b1fbb64ae
--- /dev/null
+++ b/Packs/FeedTAXII/ReleaseNotes/1_1_9.md
@@ -0,0 +1,4 @@
+
+#### Integrations
+##### TAXII 2 Feed
+- Documentation and metadata improvements.
diff --git a/Packs/FeedTAXII/pack_metadata.json b/Packs/FeedTAXII/pack_metadata.json
index c0cf934641f2..86a27f003156 100644
--- a/Packs/FeedTAXII/pack_metadata.json
+++ b/Packs/FeedTAXII/pack_metadata.json
@@ -2,7 +2,7 @@
     "name": "TAXII Feed",
     "description": "Ingest indicator feeds from TAXII 1 and TAXII 2 servers.",
     "support": "xsoar",
-    "currentVersion": "1.1.8",
+    "currentVersion": "1.1.9",
     "author": "Cortex XSOAR",
     "url": "https://www.paloaltonetworks.com/cortex",
     "email": "",