As many of you know, I am a Russian, so English is not my native language, so SE website may has some grammar errors. If you are native English speaker, had 'A' mark at English in school, and want to contribute, this thread for you. HarbingerDawn and DoctorOfSpace are helping me in this, but we need more help...

To simplify work, I will upload a page source code by a request. Please ask here for a page you want to fix, and I will attach the html file. You can open it with some editor (Notepad++ has a syntax highlight) and go through it fixing the language. But please don't break the html tags. You may check the code on this site: copy/paste html code to the corresponding window, and this code to CSS:



If you will see broken formatting or a large coloured blocks, them you seems broke something. Note that this site CMS uses some pseudocode on pages, which looks like this: [vc_column][no_accordion active_tab="1"], don't break this too.

Also, to simplify/speedup the work, you may cooperate with other users. Split the file to several parts and fix them separately.

Because the forum is large now, and I have no time to read through all threads, I may not respond during weeks. But if you refer my name in your post (press on my nickname and choose 'Refer by username'), I will be notified by the forum what someone need my attention (the bell icon on the top of the page).

Lets start with a newly added SE 0.981 scenario scripts tutorial:



Forum doesn't allow to attach html by security reasons, so I changed extension to txt.

Other tutorials are here:

This page describes the new functionality introduced in the upcoming SpaceEngine 0.981, which has not been released yet.
This manual describes how to make a scenario scripts in SpaceEngine. Before continuing, it is recommended to that you read this manual: 

Introduction
SPACEENGINE CONSOLE AND *.SE FILES
SpaceEngine 0.981 introduced a new type of files – *.se. It is  – a scenario script files, which contains a code which that is could be executed by SpaceEngine. A great example of what scenarios are capable to is are the Tutorials, introduced in 0.981. The default location for *.se files is data/scripts/ or addons/*/scripts/ folder. You can run *.se files from SpaceEngine by opening the console ([~] key by default) and typing this command:

Code
run filename

If the file filename.se exists in the mentioned folders, it will be executed. Another way to run *.se files is by passing them to SpaceEngine’s executable through command line arguments. The best way to do that is to associate the *.se extension with SpaceEngine.exe in your system. In that case, double-clicking on the file will launch SpaceEngine and order it to execute the scenario script. If SpaceEngine is already running, this running instance will execute the script.
All commands could can be executed in the ‘direct mode’ by typing them in the console, or executing them from a *.se script file. Commands and most of their parameters are not case-sensitive, but string constants such as names of GUI widgets and names of triggers are case-sensitive.
Some commands can have (or even must have) an additional parameters, provided in the curved braces block (i.e. that those commands are actually tags). Example:

CodeGoto
{

Time 5.5
Dist 25000
}

Additional parameters could can be typed in a single row:
CodeGoto { Time 5.5 Dist 25000 } Using the single-row style sometimes makes the script code more compact and easy to read and understand.
All commands are split in a groups according to their functions. Unroll the blacks below to read details.

I will work my way through each section over the next couple of days and it will be perfect. 

(if you want to make me a beta tester as a reward, I'd very much like that if not, don't worry I will still do it, because I love to contribute to this)

As you can see, I didn't read your instructions. I'll try and work through the whole thing, but if the other people working on it could tell me what sections they are doing, I can do the rest

SpaceEngineer, you spelled the word "spellcheck" wrong in the title of this topic I am afraid i cannot help very much though, English is not my native language But i really want to help.

^ I was going to point that out myself but I was afraid it was a practical joke and I didn't want to be the first one to fall for it xD

LOL Dr. Kaii Anyway, thanks for help!

SpaceEngineer wrote:

LOL Dr. Kaii Anyway, thanks for help!

Hey at least with my one you can learn and improve your grammar

Yeah I must learn articles and times better...

SpaceEngineer wrote:

Yeah I must learn articles and times better...

When you are engineering an entire universe, you haven't got much time spare to learn the finer points of grammar, so it's understandable (it would also help if English could stick to its own rules half the time). 

HarbingerDawn and DoctorOfSpace please be in touch with me and assign me some parts of the manual to do. I'm not going to waste any more time doing stuff incorrectly

Dr. Kaii,feel free to do any and just post as usual.  Harb is quite busy as of late and I have a lot of other things to do, not just SE related.

Ok it looks like it's just me and 50-100 pages. I am happy to commit

Ok the first one is done. Please send the rest. 

It too me 1 hour 40 minutes to do 1000 lines, so that's a rough guide to how long the rest will take. I can do a few hours a week. If it's just the "modding" section that needs doing, then it shouldn't be more than another 2000 lines or so I estimate.