There is inconsistency between v2.8.1 and v3.3.1

It is found that there is an inconsistency in the code between v2.8.1 and v3.3.1 as below.

<api-tests/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot>

[v2.8.1]

*** Test Cases ***
Instantiate a vnfInstance
    [Documentation]    Test ID: 7.3.1.3.1
    ...    Test title: Post Instantiate Individual VNFInstance 
    ...    Test objective: The objective is to instantiate a VNF instance
    ...    Pre-conditions: VNF instance resource is in NOT INSTANTIATED state
    ...    Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v2.8.1
    ...    Config ID: Config_prod_VNFM
    ...    Applicability: none
    ...    Post-Conditions: none
    POST instantiate individual vnfInstance
    Check HTTP Response Status Code Is    202
    Check HTTP Response Header Contains    Location                                <==== Inconsistent line
    Check Individual VNF LCM operation occurrence operationState is    STARTING    <==== Inconsistent line

[v3.3.1] (v2.6.1 as well)

*** Test Cases ***
Instantiate a vnfInstance
    [Documentation]    Test ID: 7.3.1.3.1
    ...    Test title: Post Instantiate Individual VNFInstance 
    ...    Test objective: The objective is to instantiate a VNF instance
    ...    Pre-conditions: VNF instance resource is in NOT INSTANTIATED state
    ...    Reference: Clause 5.4.4.3.1 - ETSI GS NFV-SOL 003 [1] v3.3.1
    ...    Config ID: Config_prod_VNFM
    ...    Applicability: none
    ...    Post-Conditions: none
    POST instantiate individual vnfInstance
    Check HTTP Response Status Code Is    202
    Check Operation Occurrence Id existence        <==== Inconsistent line

I think this inconsistency should be resolved by changing code in either version.