Urgent help with quick translation questions

Question

Hello,
I am somewhat new to Java. I have a translation to hand in in a few hours (French to English). Argh! I have questions on how I worded some parts of the translation (and also if I understood it right). Could you, great developers, please take a look and see if what I wrote makes sense? I've put *** around the words I wasn't sure about. If it sounds strange or is just plain wrong, please let know. I also separated two terms with a slash, when I was in doubt of which one was the best.
Many thanks in advance.
1) Tips- Always ***derive*** the exceptions java.lang.Exception and java.lang.RuntimeException.
Since these exceptions have an excessively broad meaning, ***the calling layers will not know how to
distinguish the message sent from the other exceptions that may also be passed to them.***
2) The use of the finally block does not require a catch block. Therefore, exceptions may be passed back to the
calling layers, while effectively freeing resources ***attributed*** locally
3) TIPS- Declare the order for SQL ***statements/elements*** in the constant declaration section (private static final).
Although this recommendation slightly hinders reading, it can have a significant impact on performance. In fact, since
the layers of access to data are ***low level access***, their optimization may be readily felt from the user’s
perspective.
4) Use “inlining.”
Inlining is a technique used by the Java compiler. Whenever possible, during compilation, the compiler
copies the body of a method in place of its call, rather than executing a ***memory jump to the method***.
In the example below, the "inline" code will run twice as fast as the ***method call***
5)tips - ***Reset the references to large objects such as arrays to null.***
Null in Java represents a reference which has not been ***set/established.*** After using a variable with a
large size, it must be ***reassigned a null value.*** This allows the garbage collector to quickly ***recycle the
memory allocated*** for the variable
6) TIPS Limit the indexed access to arrays.
Access to an array element is costly in terms of performance because it is necessary to invoke a verification
that ***the index was not exceeded.***
7) tips- Avoid the use of the “Double-Checked Locking” mechanism.
This code does not always work in a multi-threaded environment. The run-time behavior ***even depends on
compilers.*** Thus, use the following ***singleton implementation:***
8) Presumably, this implementation is less efficient than the previous one, since it seems to perform ***a prior
initialization (as opposed to an initialization on demand)***. In fact, at runtime, the initialization block of a
(static) class is called when the keyword MonSingleton appears, whether there is a call to getInstance() or
not. However, since ***this is a singleton***, any occurrence of the keyword will be immediately followed by a
call to getInstance(). ***Prior or on demand initializations*** are therefore equivalent.
If, however, a more complex initialization must take place during the actual call to getInstance, ***a standard
synchronization mechanism may be implemented, subsequently:***
9) Use the min and max values defined in the java.lang package classes that encapsulate the
primitive numeric types.
To compare an attribute or variable of primitive type integer or real (byte, short, int, long, float or double) to
***an extreme value of this type***, use the predefined constants and not the values themselves.
Vera

Answer 1

1) Tips- Always ***derive*** the exceptions java.lang.Exception and java.lang.RuntimeException.***inherit from***
***the calling layers will not know how to
distinguish the message sent from the other exceptions that may also be passed to them.***That's OK.
while effectively freeing resources ***attributed*** locally***allocated*** locally.
3) TIPS- Declare the order for SQL ***statements/elements*** in the constant declaration section (private static final).***statements***, but go back to the author. There is no such thing as a 'constant declaration section' in Java.
Although this recommendation slightly hinders reading, it can have a significant impact on performance. In fact, since
the layers of access to data are ***low level access***, their optimization may be readily felt from the user’s
perspective.Again refer to the author. This isn't true. It will make hardly any difference to the performance. It is more important from a style perspective.
4) Use “inlining.”
Inlining is a technique used by the Java compiler. Whenever possible, during compilation, the compiler
copies the body of a method in place of its call, rather than executing a ***memory jump to the method***.
In the example below, the "inline" code will run twice as fast as the ***method call***Refer to the author. This entire paragraph is completely untrue. There is no such thing as 'inlining' in Java, or rather there is no way to obey the instruction given to 'use it'. The compiler will or won't inline of its own accord, nothing you can do about it.
5)tips - ***Reset the references to large objects such as arrays to null.***Correct, but refer to the author. This is generally considered bad practice, not good.
Null in Java represents a reference which has not been ***set/established.******Initialized***
After using a variable with a
large size, it must be ***reassigned a null value.*** This allows the garbage collector to quickly ***recycle the
memory allocated*** for the variableAgain refer author. Correct scoping of variables is a much better solution than this.
***the index was not exceeded.******the index was not out of range***
The run-time behavior ***even depends on compilers.***Probably a correct translation but the statement is incorrect. Refer to the author. It does not depend on the compiler. It depends on the version of the JVM specification that is being adhered to by the implementation.
Thus, use the following ***singleton implementation:***Correct.
it seems to perform ***a prior initialization (as opposed to an initialization on demand)***.I would change 'prior' to 'automatic pre-'.
***this is a singleton***That's OK.
***Prior or on demand initializations***Change 'prior' to 'automatic'.
***a standard
synchronization mechanism may be implemented, subsequently:***I think this is nonsense. I would need to see the entire paragraph.
***an extreme value of this type******this type's minimum or maximum values***
I would say your author is more in need of a technical reviewer than a translator at this stage. There are far too serious technical errors in this short sample for comfort. The text isn't publishable as is.