doc: minor improvements in BUILDING.md

[thefourtheye]

1. necessarily reliably => necessarily reliable
2. projects root directory => project's root directory
3. remove console highlighting, as test alone is highlighted
4. fix broken link for Android NDK
5. highlight the directory location /usr/local/ssl/fips-2.0
6. remove expected output for process.versions.openssl as the version
   displayed is not mentioned in the document

Checklist

• documentation is changed or added
• commit message follows commit guidelines

Affected core subsystem(s)

doc

---

cc @mhdawson

[mhdawson]

LGTM

[gibfahn]

9. Verify with node -p "process.versions.openssl"

Maybe specify how you know the build was done in FIPS mode? Maybe:

9. Verify that the openssl version contains "fips": node -p "process.versions.openssl" (for example1.0.2a-fips)

[thefourtheye]

Ack

[Trott]

I think reliably is the correct word here. A fuller sentence would be: This is known to compile but it does not necessarily compile reliably or with a full passing test suite.

That said, all the qualifiers (known to, not necessarily, reliably...) are redundant. Maybe replace the whole sentence with something like this?:

May not compile reliably. Test suite may not pass.

[thefourtheye]

I changed it to May not compile reliably or test suite may not pass.. Is that okay?

[Trott]

I'm pretty sure I'm the one that added console. The idea was to distinguish between something that was a command (such as make test) and something which was console display (as it is here because it includes the $ prompt).

All that said, I don't actually care if it goes away. :-D

[UPDATE: Nope, I'm wrong about it being me; git blame says it was @ChALkeR.]

[thefourtheye]

Mmmm, I am leaving this as it is for now.

[gibfahn]

Could you do it like:

Download and extract the
[Android NDK](https://developer.android.com/tools/sdk/ndk/index.html),
then run:

? That way you keep it <80 chars and the link should still work.

[thefourtheye]

Ack

[thefourtheye]

Landed in ba0e3ac