I think i got your answer..Thanks to google and stackoverflow.
A WPF FlowDocument can only belong to a single RichTextBox. But if you are using a single document which can be manipulated at different points in the UI, then it will not happen that there are two RichTextBoxes simultaneously displaying a single document (and can't, because WPF will complain). But are you using a single document or multiple? if single, read the rest and if not, well, move along.
Using a MemoryStream and XamlReader/Writer won't work here as we would like to retain a single document and reflect changes wherever it is used, so copying it every time is out.
Copied from a member Jared of stackoverflow,
WPF controls can be ‘unparented’ and ‘reparented’ at will, so just make the RichTextBox instance available in the context shared throughout your wizard and make sure you unparent / reparent as you move from page to page. This also has the benefit of saving any styles or changes to the editors state across pages in the wizard (which is probably desirable).
If it isn’t possible to share the RichTextBox instance across pages, I think there is a way to disassociate the document from the original RichTextBox. It appears that in order to disassociate the document from RichTextBox1, you have to provide RichTextBox1 with a new document. You can’t set RichTextBox1.Document to null, but you CAN set RichTextBox1.Document to new FlowDocument() and I believe that will work.
From the above, FlowDocument cannot be shared by several RichTextBox controls directly..
So as i comment above, use grid
<Grid>
<Grid.ColumnDefinitions>
<ColumnDefinition />
<ColumnDefinition />
</Grid.ColumnDefinitions>
<Grid.RowDefinitions>
<RowDefinition />
<RowDefinition Height="Auto" />
</Grid.RowDefinitions>
to wrap the RTB and in the code behind use
FlowDocument doc = RTB1.Document;
RTB1.Document = new FlowDocument();
RTB2.Document = doc;
i don't know whether this will split the control but we can see the document(single) in another RTB.