1. Lack of information.

   - Lack of console screenshots for topics about console element

   - Lack of steps for different operating systems

    - Lack of detailed guidance, but only with ambiguous information

    - Lack of description about architecture or how to work

    - Command variables are not explained

   - Diagram is not in detail

2. Wrong information.

   - Typo errors

  - Information in docs is not consistent with user’s environment

  - Outdated product names

  - Information in docs is wrong itself

3. Confusing information.

   - Steps are not in details. Users might have different understandings

  - Terms with the same meaning, but with different names

  - Commands with variables and designated values, but without explanations.

4. Other feedbacks.

   - Broken Links

   - Slower loading speeds than before

   - Bad search results

5. Improvement solutions:

  - Peer review process is necessary.

  - Adopt more automatic Acrolinx and broken link checking process, and ensure each docs pass Acrolinx and broken link checking before they are published.

  - Pain points, peer review results, and best practices discussion and sharing.

  - Most users use the search function in Docs site, instead of Google search.

  - Investigate the search function in Docs site, and summarize the problems for improvements.

  - More convenient communication channels with Sales, pre-sales support, post-sales support team to get more real-time feedbacks more quickly and easily.

  - Add  more high-quality topics to help users have a better understanding of the  architecture, concept, purpose, workflow graph,  use scenarios for each feature, security  concerns,etc, instead of providing only the procedure to complete a task.

  - Get the email address of the users that provide negative feedbacks, and check

  with them for detailed suggestions.