INK's proprietary AI analyzes your text while you write, making it simple for you to check for spelling mistakes and sentence structure. 

How do I use INK's Text Review Feature?

One way of using this tool is through the word tasks function on the right-hand sidebar

This tool will give you suggestions on how to optimize your text by fixing spelling errors or improving your word count. 

You can also view a more in-depth analysis of this feature by clicking on the Grammar tab in INK. 

By clicking on this tab, you will see an in-depth analysis of your writing and exactly where your spelling issues are located within the text. This is one of the best ways of using INK to improve and optimize your content. 

As well as these two features, INK also has another text review system for a full analysis of your content. 

If you navigate to the tools tab in INK and click on the Text Composition feature, it will show you a full analysis of your work. 

As you can see below, this feature will show you everything you need to know about your text, from your adverb usage to your word count. 

All of these features help you to get the most out of INK and your content, making your text as optimized as possible. 

But, how does it work?

How INK's Text Analysis Works

For the most part, INK's AI uses your local system to do most of the heavy lifting when it comes to text analysis. The inbuilt features within the INK app allow you to review your text seamlessly and often without interruption. 

Even with a large text system, INK can seamlessly check your work for spelling errors, issues, and syntax problems. 

However, when analyzing your text, we do use our cloud servers to check some aspects of your work. This means that if you are offline, INK's text analysis feature won't work to its full potential, so it's best to stay connected to get the most out of the app. 

If you have any questions about INK's text reviewing AI or how to make the most of this feature, please don't hesitate to send us a feedback form through the INK app. 

Did this answer your question?