Merge pull request #34 from ppival/patch-10

Fix typos and enhance clarity in Imports and Exports doc

Author: ccbogel

docs/doc/en/6.1.-Imports-and-Exports.md

@@ -53,7 +53,7 @@ For audio and video, importation of transcriptions and syncpoints is untested. I
 
 To import, close any currently opened project first. Then choose a new QualCoder project name, then select the qdpx import file.
 
-If no coded data is visible, you may need to change the current coder's name in Settings.Try the drop down coder name box.
+If no coded data is visible, you may need to change the current coder's name in Settings. Try the drop-down coder name box.
 
 This is now old (Feb 2021), but a user tested the importation of a REFI-QDA project file generated by QualCoder and imported into MAXQDA, Quirkos, Atlas.ti. Only text and Images were tested. A PDF of the test results is here: [Testing importation of REFI-QDA Project files into Atlas, MAXQDA, Quirkos PDF](https://qualcoder.files.wordpress.com/2021/02/refi-qda-project-import-quirkos-maxqda-atlas.pdf)
 
@@ -68,7 +68,7 @@ If no coded data is visible, you may need to change the current coder's name in
 
 This requires a CSV or Excel (xlsx format) file. You can try importing the survey.csv file in the Examples folder.
 
-Survey files in a CSV format, are comma delimited, another delimiter can be chosen. For tab-delimited files type ta, tb, or tab in the Delimiter box so that QualCoder knows the csv file is tab delimited. **The first row must contain the headings for attributes. The first column must contain the unique identifiers for each survey respondent.**
+Survey files in a CSV format are comma delimited, another delimiter can be chosen. For tab-delimited files type ta, tb, or tab in the Delimiter box so that QualCoder knows the csv file is tab delimited. **The first row must contain the headings for attributes. The first column must contain the unique identifiers for each survey respondent.**
 
 CSV quoting format can be NONE, MINIMAL or ALL. examples of each are shown below, please open your CSV file with a text editor or similar to check how it has been prepared.
 
@@ -90,16 +90,16 @@ QualCoder cannot determine if an attribute is qualitative data. You must right-c
 
 ![image](https://github.com/user-attachments/assets/ae540730-b58c-484e-9beb-8aa40093e94d)
 
-The default option, is that each qualitative response for each row, will be stored in its own text file entry in the qualcoder database. This file will be attached to each case (each survey row entry, with the unique ID)
+The default option is that each qualitative response for each row will be stored in its own text file entry in the QualCoder database. This file will be attached to each case (each survey row entry, with the unique ID)
 
 When you click on the OK button, the cases and their attributes will be added. 
 
 ### Older versions of QualCoder, e.g. QualCoder 3.5.
-Each qualitative question answer was appended to ONE text file. Preceding the answer was additional QualCoder added text, to show which case the answer was relevant to. 
+Each qualitative question answer was appended to ONE text file. Preceding the answer was additional QualCoder-added text to show which case the answer was relevant to. 
 
 In this format: _[unique id] The qualitative text._
 
-Open Manage Files, then View that file, and you will see the case assigned text is underlined in green.
+Open Manage Files, then View that file, and you will see the case-assignment text underlined in green.
 
 ![image](https://github.com/user-attachments/assets/5c05347a-731b-40d8-943f-921409447403)
 
@@ -108,7 +108,7 @@ Open Manage Files, then View that file, and you will see the case assigned text
 
 Import a bibliography. This must be in RIS formatted plain text. The file can have endings of .txt or .ris
 
-In the menu, go to Manage > Manage references. Press the import button: This has the icon of arrow on top of a document.
+In the menu, go to Manage > Manage references. Press the import button: This has the icon of an arrow on top of a document.
 
 Select the file.
 
@@ -121,19 +121,19 @@ In here you can link (and unlink) references to files. You can manually edit an
 Once this is imported and files are linked to references, go to the Manage Files screen.
 In here there will be four new attribute columns: Ref_Authors, Ref_Title, Ref_Type, Ref_Year
 
-Files link to references will have details in those columns.
+Files linked to references will have details in those columns.
 
 ## Help - Special Functions
 
 ### Dynamic update text content
 
-This is useful for updating text files such as blog post extract that change over time. Update a text file while attempting to keep the existing coded text segments. Select the text file that needs to be replaced and select the replacement file. Click the cogs button to run the update. This function works by finding the identical matching text in the replacement file, as it parses through the file text. It may produce erroneous  coded segments.
+This is useful for updating text files, such as blog post extracts, that change over time. Update a text file while attempting to keep the existing coded text segments. Select the text file that needs to be replaced and select the replacement file. Click the cogs button to run the update. This function works by finding the identical matching text in the replacement file as it parses through the file text. It may produce erroneously coded segments.
 
 ### Merge QualCoder Projects
 
 Select a QualCoder project to merge (source project) into the currently opened project (destination project), then click the _Run merge projects_, cogs button. **Before performing the merge, make a backup of the destination project.**
 
-Caution: If each project to be merged has the same coder name, e.g. 'default' then these will merge as such, and you will not be able to separate out which coder performed their own coding. This may or may not be an important consideration to your final merged project.
+Caution: If each project to be merged has the same coder name, e.g., 'default', then these will merge as such, and you will not be able to separate out which coder performed their own coding. This may or may not be an important consideration to your final merged project.
 
 The following occurs:
 
@@ -149,9 +149,9 @@ The following occurs:
 Considerations before merging:
 
 Ideally, everyone would have the same identical files within the project.
-Ideally using the same set of code names - but this could be worked around later if merging or renaming codes occurred in the collated project.
-Coder names - would need to be unique for each coder. So, when collated the individual coders work can be identified.
-Alternatively, coder names could be the same, providing they each worked on unique files to code. But that all depends on your end goals really. If you had a need to collate all under one coder name.
+Ideally, using the same set of code names - but this could be worked around later if merging or renaming codes occurred in the collated project.
+Coder names - would need to be unique for each coder. So, when collating the individual coders' work can be identified.
+Alternatively, coder names could be the same, provided each coder worked on unique files. But that all depends on your end goals, really. If you had a need to collate all under one coder name.
 
 Warnings when merging: